On Wednesday 28 April 2010, Derek Atkins wrote: > Geert Janssens <[email protected]> writes: > > -GNUCASH_LATEST_STABLE_VERSION="2.2.9" > > +GNUCASH_LATEST_STABLE_SERIES=$GNUCASH_MAJOR_VERSION.$(($GNUCASH_MINOR_VE > >RSION-($GNUCASH_MINOR_VERSION%2))) > > This logic will fail when we go from 2.x -> 3.0 > > I'd rather this be "hard coded" and we just have a list of places where > we need to "fix" the release number when we make a new stable release. > > I think we just need a release engineering checklist somewhere (the wiki)? > > -derek > I'm not sure it will fail.
The unstable series leading up to 3.0 will be 2.9. While developing 2.9, the previous stable series will be 2.8, which will be calculated correctly. The next unstable series will be 3.1, and the stable series preceding that will correctly be calculated as 3.0. Geert _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
