I think I too side with option 1. As much as I would enjoy googleizing our naming scheme and adding beta to the end of every initial release I don't think it is practical for our product. While enhancements are an important part of Koha I don't believe we should put them ahead of its stability.
On Thu, Jul 12, 2012 at 5:58 AM, Fischer, Katrin <[email protected]>wrote: > Hi all, > > I agree with Chris on option 1). > > We should always aim for the most stable release possible. Part of that is > to add more automated tests and to get our human testing better organized. > > I think releasing a beta will mean that we will end up pushing risky > things to that version, because there will still be time to fix it. So it > will take even longer, until we reach a stable release. Also, if something > is named "beta" or "RC", I think we are unlikely to get libraries to use > and test it. So it looks to me like we would be losing time and losing 2 > releases that could be great. > > Going into feature freeze earlier like suggested as option 1) is only > about announcing too - it requires no change at all, not even a change in > naming. And whenever we announce freezes - it will always be too early for > some features and things we wanted to do for this next version. > > Katrin > > > > -----Original Message----- > > From: [email protected] [mailto:koha-devel- > > [email protected]] On Behalf Of Chris Cormack > > Sent: Thursday, July 12, 2012 12:22 PM > > To: Marcel de Rooy > > Cc: [email protected] > > Subject: Re: [Koha-devel] About Release process > > > > * Marcel de Rooy ([email protected]) wrote: > > > Hi Paul, all, > > > > > > > * Release the 3.X.0 saying it's a beta, could have some bugs not > > detected. The 3.X.1 being a RC, and the 3.X.2 being the 1st really > > stable version. > > > +1 for this second option. You could say that it makes more formal > > > +what one could already suspect about a 3.X.0 release.. No real change > > > +in workflow.. (3.X.1 being stable might be nice too :-) > > > > I think I prefer the first option, or at least that is what we should be > > aiming for. Aiming for a stable release at the .1 or .2 level will mean > > it wont be stable until .3 or .4. > > > > But as the elected release manager for 3.10.0 it's your call, and I will > > work with whatever you decide. > > > > I think this is also a good time to start thinking about 3.12.x > > > > http://wiki.koha-community.org/wiki/Roles_for_3.12 > > > > Chris > > > > > > -- > > Chris Cormack > > Catalyst IT Ltd. > > +64 4 803 2238 > > PO Box 11-053, Manners St, Wellington 6142, New Zealand > _______________________________________________ > Koha-devel mailing list > [email protected] > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Elliott Davis Development Support Specialist [email protected] 903.571.4257
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
