Life of an issue
The GWT project maintains a public issue tracker where you can report bugs and request features for GWT.
Issue reporting guidelines
One of the best ways you can help us improve GWT is to let us know about any problems you find with it.
Here’s how to report issues:
- Search for your issue to see if anyone has already reported it.
- If no one’s reported your issue, file it. Please provide the versions of GWT, the browser(s), and the platform(s) used. It is especially important to provide the browser version(s) and a small code sample which can be used to reproduce the issue. If the issue has been discussed in forums, please provide a link to the discussion too.
To see what happens to your issue once you report it, keep reading.
What happens when you submit an issue
Here’s the Life of an Issue, in a nutshell:
- An issue is filed.
- A GWT contributor periodically reviews and triages issues. The GWT contributor attempts to verify the issue and assigns a status based on the results.
- Once an issue has been verified, it may be marked Accepted, in which case the GWT team plans to fix it, or PatchesWelcome, which means that the GWT team likely won’t be able to get to it, but would be happy to review patches from the community. To submit a patch, follow these guidelines.
- Once an issue has been fixed, it’ll be closed and assigned to a milestone, indicating whether the fix is available in the current numbered release or, more commonly, in the Git master branch for the next release.
The following tables provide detail on all issue status types.
Open Issues
| Status | Description |
|---|---|
| Issue has not had initial review yet | |
| Accepted | Problem reproduced / Need acknowledged |
| Started | Work on this issue has begun |
| PatchesWelcome | Confirmed and triaged, but not assigned. Feel free to submit patches for review. |
| ReviewPending | Commit gated by code review |
| NeedsInfo | Additional information is required from submitter |
Closed Issues
| Status | Description |
|---|---|
| Fixed in associated milestone (could be a future release of GWT) | |
| NotPlanned | No current plans to address this issue |
| Invalid | This was not a valid issue report (e.g. illegible, spam, does not describe a real issue) |
| AssumedStale | Assumed (perhaps incorrectly) to no longer be a problem; please reconfirm with latest release |
| AsDesigned | The feature is behaving as intended |
| KnownQuirk | Not denying it's a real issue, but likely a browser quirk beyond our control to fix efficiently |
| Duplicate | This report duplicates an existing issue |
| CannotReproduce | The issue could not be reproduced based on the report |
Other Stuff
The states and lifecycle above are how we generally try to track software. However, GWT contains a lot of software and gets a correspondingly large number of issues. As a result, sometimes issues don’t make it through all the states in a formal progression. We do try to keep the system up to date, but we tend to do so in periodic “issue sweeps” where we review the database and make updates.
Occasionally, we make tweaks to the list of issue states and the lifecycle described above. When we do this, we’ll update this page as well.