Here, check this out:
https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob_plain;f=acinclude.m4.in;hb=HEAD Specifically, these lines: m4_define([LOCAL_VERSION_MAJOR], [1]) m4_define([LOCAL_VERSION_MINOR], [3]) m4_define([LOCAL_VERSION_REVISION], [0]) m4_define([LOCAL_VERSION_STAGE], [a]) m4_define([LOCAL_VERSION_RELEASE], [-%release%]) These set up the version number for the build. So, if you built it at the moment, it would generate this version number: 1.3.0ad4cdb2b-git The %release% is populated by our bootstrap script: https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob_plain;f=bootstrap;hb=HEAD Specifically these lines: if test -z "$REVISION"; then if test -d .git; then REVISION=`git describe --always`-git else # default to svn REVISION=`\`which svn\` info . 2> /dev/null | awk "/Revision:/{print \\$2}"` fi fi if test -z "`get LOCAL_VERSION_STAGE`" -o -z "$REVISION"; then sed "s/%release%//" < acinclude.m4.in > acinclude.m4 else sed "s/%release%/$REVISION/" < acinclude.m4.in > acinclude.m4 fi Now, what we do when we're making a release is that on the release branch, we change the original to: m4_define([LOCAL_VERSION_MAJOR], [1]) m4_define([LOCAL_VERSION_MINOR], [3]) m4_define([LOCAL_VERSION_REVISION], [0]) m4_define([LOCAL_VERSION_STAGE], []) m4_define([LOCAL_VERSION_RELEASE], []) Which, when built for voting, produces: 1.3.0 So, in summary, by default, our source automatically appends an alpha version number. And when we're doing a release, we temporarily remove that, cut the release, and then bump the release number, and put it back in again. I believe a similar system, irrespective of implementation, could work for us here? On Mon, Oct 1, 2012 at 4:35 PM, Chip Childers <chip.child...@sungard.com>wrote: > On Sun, Sep 30, 2012 at 11:54 AM, Noah Slater <nsla...@tumbolia.org> > wrote: > > Do we intend to release anything with the version 4.0.0.beta1? If not, > you > > could change it to 4.0.0. It is fine for the source to be configured to > > display "4.0.0" and preparations of that source to say "4.0.0" even > though > > it has not been released yet. (As long as those preparations/builds are > not > > distributed to end users. Posting to this list is obviously okay.) > > As a developer, I like having some sort of revision number to let me > know what I've downloaded. For these builds, I would prefer to have > that distinction in the file name. The internal code references > version 4.0.0, so that is in like with your note above. > > > On Wed, Sep 26, 2012 at 4:01 PM, Chip Childers < > chip.child...@sungard.com>wrote: > > > >> All, > >> > >> For those of you helping review the source code for legal / policy > >> compliance, I've posted a new source code only package (4.0.0.beta1) > >> here: > >> > >> http://people.apache.org/~chipchilders/cloudstack/4.0/ > >> > >> As always, we will rely on community support to host binary builds > >> from these source packages. > >> > >> -chip > >> > > > > > > > > -- > > NS > -- NS
