Stan The process we have in mind is that if the bug is **really** important then it will be fixed in 1.1 and 1.0. We did that in the past for Squeak 3.9. Now normal improvements changes.... will not be retro-ported because we simply cannot. And you are right to report a bug it is important in the future that people check if the bug is already fixed in the current unstable else we will not be able to make process and we will spend our time testing. Mariano we should update the web page how to submit a bug...
>>> >> > > Hi Mariano, I suppose my question was mainly about how to keep that 1.0 > version up with its current fixes. Is it a question of watching out for a > new release on the downloads page. > > It would be preferable to pick up all updates (semi)automatically, in which > case you know that a bug you hit is still a bug. > > I know I have seen bugs such as the one I just logged, but felt they were > likely already in the works, or caused by something I'd done. If I can > easily keep an image as the 'gold standard' of where a patched up to date > image should be, I'm more likely to decide something really is a bug and log > it. > > Cheeers, ...Stan > > -- > View this message in context: > http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-support-the-creation-of-new-method-cat-tp4194364p4200841.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
