That's a good question I was also thinking about today... I suggest the following steps:
1. Review all issues in the tracker and decide for each whether it is important for 1.0. 2. We concentrate on completing these 1.0-tagged items. New issues should only be tagged with 1.0 if they are critical bugs (i.e., no new improvements get integrated anymore!) 3. As soon as we have completed all items that change the behavior of the system (i.e., that are not bugfixes) we declare beta 4. As soon as all items are done, we declare gamma and after a while without newly reported problems we release 1.0 Adrian On Jun 11, 2009, at 21:59 , Stéphane Ducasse wrote: >> >> Marcus, Adrian, Mike >> how do we proceed to go beta? >> take the 1.0 fixes and integrate them. >> put a deadline and do it? >> >> Stef >> >> >> > > > _______________________________________________ > 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
