On Fri, Aug 5, 2011 at 8:56 AM, Øyvind Harboe <oyvind.har...@zylin.com>wrote:
> When I run git describe now I get v0.4.0-973-g0d7a948 rather than > a v0.5.0-rc2-xxxx. > > Is that intentional? > > I think it's nice that we stick to v0.4.0-xxxx until v0.5.0-xxxx goes out > of the door. > > I have no particular opinion, except it should be by choice and not > by accident :-) > > As I posted several times already, it's because the release procedure wasn't followed in creating the rc tags and tarballs. The following basic steps should be followed for a proper rc3 release. There are more things to take in consideration, for example making sure the NEWS file is properly updated and so on. Check the release manual that Zach and David wrote. 1. Manually fix, commit and push the skipped version bumps in configure.in: -AC_INIT([openocd], [0.5.0-dev], +AC_INIT([openocd], [0.5.0-rc3-dev], 2. do a fresh git clone of openocd 3. run tools/release.sh --next rc release 4. verify and publish archives/* 5. merge v0.5.0-rc4-dev into master and push it After this, git describe correctly reflects that we're in rc phase: v0.5.0-rc3-1-gbcded6a And version strings should be correct (didn't test): 0.5.0-rc3 if built from tarball, 0.5.0-rc4-dev if built from git HEAD. I think we really need to do this, like, right now, then wait for feedback from people building the released rc3 tarballs (a week tops), then do the final 0.5.0 release. No patches accepted except build and packaging fixes after rc3 is out. Final 0.5.0 release is very similar: 1. do a fresh git clone of openocd 2. run tools/release.sh --next minor --final release 3. verify and publish archives/* 4. merge v0.6.0-dev into master and push it /Andreas
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
