Mariano Martinez Peck wrote: > > As already said several times. For me, we have to: > > 1) Put ALL our effort and or priority to release the 1.0 stable. This > means, > try to fix the 1.0 opened fixes. > >
What is the suggested workflow for those of us who want to work off the stable version, and feedback where we find outstanding issues? I would expect to try out the offending code in a 'patched up to date' version of 1.0, to see if it is reproducable there, in which case a search of open bug reports, and possibly a new bug report, would be in order. Is there an easy way to maintain such an up to date version 1.0, with harvested bug fixes? ...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-tp4194364p4200478.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
