Your explanation makes perfect sense. The folks who submitted patches also have a legitimate claim also and should not take it personally . But, when there are so many issues, and the transition of the project to the steering committee, it only make sense to start a new bug tracker and not inherit the issues moving forward from there. Anyone with outstanding patches should bring them forward to the new issue tracker if they are still relevant. This shifts the burden of thousands of issues to many more people for investigation rather than the few who can implement the patches.
Just my 2c ed On Sun, Jun 9, 2013 at 12:12 PM, Timothy Spear <n61...@gmail.com> wrote: > Mauro, > > I am going to be slightly cheeky here. > http://www.youtube.com/watch?v=V2f-MZ2HRHQ > > At the end of the day. The public issue tracker that was available was not > being managed and was largely not maintainable or sustainable in the > current form. Google felt an obligation to turn over an issue tracker in a > more sustainable and manageable form. > > To clean up the issue tracker Google had three basic choices. > 1. Invest massive amounts of man power to triage each issue and make > determinations themselves. Including fixing/patching or prioritizing. This > is not practical from both a resource and a public perception standpoint. > If Google puts in the resources, they will not be rewarded because too many > people will object to how Google's triage the issues. > 2. Start a new issue tracker. This loses all history, and there would be > massive screaming and objections. > 3. Close everything over a certain age, tell people to submit patches > and/or reopen them. > > > Tim > > > On Sun, Jun 9, 2013 at 11:14 AM, Mauro Molinari <mauro...@tiscali.it>wrote: > >> Il 09/06/2013 14:48, Johannes Barop ha scritto: >> >>> I had some free time lately where I wanted to work on some random issue. >>> It turned out that it is very hard to find one because all of junk >>> floating around in the tracker. >>> >> >> I still don't understand (and never will) why old non-fixed bug reports >> should be considered "junk". I won't bother to open a new issue again if >> this is the case. >> >> Mauro. >> >> -- >> 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+**unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> >> . >> To post to this group, send email to google-web-toolkit@** >> googlegroups.com <google-web-toolkit@googlegroups.com>. >> Visit this group at http://groups.google.com/** >> group/google-web-toolkit?hl=en<http://groups.google.com/group/google-web-toolkit?hl=en> >> **. >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> > -- > 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+unsubscr...@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. > > > -- 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+unsubscr...@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.
