On Fri 31-Jul-2009 at 23:31 -0400, Yuval Levy wrote: >> >> Current trunk becomes 2009.1.0 immediately. > >means no freezes on trunk, ever?
That's the point of stabilising releases on branches. >> Next stable branch is 2009.2.0 as soon as it branches, trunk becomes >> 2009.3.0 at the same time. > >Just to make sure we're on the same page: the branch becomes 2009.2.0 >*before* it is actually stabilized? (see the attached image that depicts >how I envision the interface between the development and release cycles)? Yes, there is no need to create new version numbers between branch points. >If the next release branch is 2009.2.0 when it is branched, how are >snapshots (alphas), betas, candidates distinguished from final? The tarball created by cmake is called hugin-2009.2.0.tar.gz, it coincidentally contains a folder called hugin-2009.2.0 For a release candidate you only want to rename that tarball to hugin-2009.2.0_rc1.tar.gz but internally it is unchanged. If you decide to make it the final release, just rename it back again and reupload. It makes sense to do beta releases the same way, just put _beta1 in the tarball filename before uploading it. >4. tag the current revision of the new release-codeline for release >(snapshot) > >$ svn copy >https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/releases/2009.2 >https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/tags/snapshot-2009.2.0.YYMMDD >-m "Branching 2009.2 for snapshot" >5. package and release snapshot I wouldn't bother with the 'tag' since the svn number serves the same purpose, but if you do tag it needs to be the other way around: 4. create snapshot tarball, note svn number. 4a. build tarball to make sure it isn't broken at a basic level. 5. rename and release tarball snapshot. 5a. `svn copy -r 1234 ...` to create a tag for future reference. Don't put the date in the tag name as this is easy to determine, use the alpha/beta/rc name as this is what people will use. >there is no reason to build/distribute packages from trunk. No need for them to be on sourceforge, but if there was the procedure would be the same. -- Bruno --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
