Hi, I know that it is always more fun to create new things than to fix small issues here and there.
Everybody seems to working on new things... but I see practically no progress being made on fixing bugs expect if google brings out a new browser. I understand that GWT is from the same company, but it is also targetting other browsers, and there are quite a lot of bugs still marked as new, or even accepted that somehow never gets fixed. Is anybody in the GWT dev team actually periodically going through the lists of bugs that are still open or not processed at all ? Open source software can only succeed if the quality improves with every release. We like to see bug fix releases once in a while without the need to make the jump to the very latest major release. Of course we are all waiting for 1.6 now that 1.5 is out of the door ... but in ongoing products we just don't jump from one big release to the next, that has way too much impact on existing code and would require us to restart the whole testing cycle. Now that I am migrating to 1.5, I noticed this bug for example: (one that I reported some time ago): http://code.google.com/p/google-web-toolkit/issues/detail?id=2257&can=4 It is marked as new, and targeted for 1.5_RC ... can I assume that this is now fixed in 1.5.3 ? I guess not ? There are many other bugs that seem to be completely forgotten as well. David --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
