Sunday, May 26, 2013

Re: Overuse of "AssumedStale" Issue Tag

Hi there,

we have announced on Google IO this year that we can to clean up the issue tracker. The issue tracker had almost 5000 open issues and its clear that it needed work. We are on a very good path with cleaning up, but this still requires a lot of work. Lot of these issues are older than 2 years and no work has been done on them.
If you feel there is an issue that was closed and should not be closed feel free to reply on the issue (I should be on cc anyway) and we will look into it. Since GWT is an open source project you can help out and supply a patch for an issue that you feel is important.

We need the issue tracker to be a viable input for things that should be done with GWT and that is not possible with the vast amount of clutter we have in there currently.

-Daniel



On Sunday, May 26, 2013 5:48:05 PM UTC+2, V.B. wrote:
Recently, I have been getting several email updates about GWT issues that I had starred. The majority of these have been because the issue was tagged as AssumedStale. I fully understand the need for such a tag, but I think it has been overused in a few cases to the point of abuse. Specifically: I noticed that some issues tagged as Accepted (or at least Planned), are now listed as AssumedStale. I think that's taking it a bit too far. My interpretation here is that the aforementioned Accepted issues are no longer going to make into GWT. Have I misunderstood the situation? If not, is anyone else concerned about this?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments:

Post a Comment