Re: Overuse of "AssumedStale" Issue Tag

I just got that AssumedStale notification about a bug that I entered (6484).  It's not fixed and it's still an issue; it makes on-demand scrolling unusable (or at least flaky) in a CellList.  I get how satisfying it is to close a bug reports, but it's not helpful to close bug reports for bugs that still exist.

On Sunday, May 26, 2013 8:48:05 AM UTC-7, 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.