On Fri, Feb 19, 2010 at 4:01 PM, mwaschkowski <[email protected]>wrote:
> Hi, > > This is a general question regarding outstanding issues in the issue > tracker - how does this thing work? I know there was an effort to > clean things up a few months ago, but I haven't seen the results of > that, if any. > The effort to get the triage process under control is still a work in progress. To give you an idea what we're looking at, there were over 180 issues submitted post 2.0. Many of them without a sufficient repro case, or simply support related questions. On top of that, we have a backlog of roughly 600 internal issues that have been reported by Googlers that we are trying to address. We've managed to triage 380 of those issues, and should have the internal issue tracker cleaned up shortly. Once we have that out of the way we're moving to the external issue tracker. We talked the internal issue tracker first because, for most issues, we know more of the history and therefore it's easy to triage. Net, net -- there's a large amount of information that we need to clean up and organize. It's going to take some time. The effort a few months ago was a broad swipe at removing items that are no longer an issue. I still have starred issues from 2006 like: > > http://code.google.com/p/google-web-toolkit/issues/detail?id=374 > > which is still in accepted status and has even been commented that it > was still present in 2.0.0-m2, but still no resolution. > "Accepted" is admittedly a bit vague. Really, John has accepted because he knows it fails within an area of the SDK that he's normally hanging out in. What you want to watch for is "Started". Or > > > http://code.google.com/p/google-web-toolkit/issues/detail?id=1405&start=100 > > which is from 2007, and was last updated with: > > Comment 9 by [email protected], Jan 05, 2009 > The close button is such a common use case, I agree we should add it. > Status: Accepted > Labels: Milestone-Planned > > What does this mean? > Planned for inclusion in an unspecified upcoming release. We know that we need to get to it, but we don't have a timeframe yet. Also vague, and not useful when the issue has been "planned" for a year. I don't want this space to become like Adobe's tracking where issues > are opened and never resolved. I don't see this as being an issue > about actually fixing the issues, just updating/clarifying the status > of current issues. > > This is an urgent issue that requires immediate attention - what can I > do to help? > Triaging issues, by identifying those that are reproducible or providing a repro case, where one doesn't exist, would be extremely beneficial. Right now, there's quite a bit of noise in the issue tracker, and legit items are being overlooked. We, much like you, want to fix this. > > Thank you, > > Mark > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
