And just to address your specific point, this configuration propagates all the way through. From the version number you see in the docs, in the web admin interface, in the CLI messages, and even in the release tarball name.
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
