On Wed, Jun 04, 2014 at 03:31:47PM +0200, Daan Hoogland wrote: > H, > > I created a test release (wishfull thinking) using the command > > sh tools/build/build_asf.sh -b 4.4 -u dahn -v 4.4.0 -s > > ~/cloudstack-4.4/cloudstack -c -t > it created a local branch called 4.4-RC20140604T1455 and a bunch of files > > ls -l /tmp/cloudstack-build/ > total 15960 > -rw-r--r-- 1 daan wheel 8158690 Jun 4 14:55 > apache-cloudstack-4.4.0-src.tar.bz2 > -rw-r--r-- 1 daan wheel 819 Jun 4 14:56 > apache-cloudstack-4.4.0-src.tar.bz2.asc > -rw-r--r-- 1 daan wheel 123 Jun 4 14:56 > apache-cloudstack-4.4.0-src.tar.bz2.md5 > -rw-r--r-- 1 daan wheel 292 Jun 4 14:56 > apache-cloudstack-4.4.0-src.tar.bz2.sha > > This is a test run so test if you wish but no vote yet > > There is a part of the release procedure not clear to me: > > Committed revision 5485. > completed. use commit-sh of c4494aae9f6b8ddebb0c1d018122cb2ee69425da > when starting the VOTE thread > > what commit-sh should I use? or is it just a ref to the id of the > commit? (i have not pushed c4494aae9f6b8ddebb0c1d018122cb2ee69425da > yet) > > -- > Daan
The commit ID pushed out is the specific commit that has the pom.xml version fixes in it. If you look at git log -3 you'll see a version fix (remove SNAPSHOT) and then another to put it back. If you were doing this for real, after confirming you are happy with the release artifact, you would push your 4.4 branch (which would contain those 2 version related commits) to origin. Make sense?
