Re: [Openstack] Stable and Development Trunks

On Thu, Feb 10, 2011 at 6:19 PM, Everett Toews wrote: > Can anyone confirm that the fix for the Missing items in Bexar release > tarball bug will cause a new nova package on ppa:nova-core/release? Yep. ___ Mailing list: https://launchpad.net/~openstack

Re: [Openstack] Stable and Development Trunks

FWIW, I've been using ppa:nova-core/releaseand it's worked pretty well with instructions for a Manual Install of Nova on Ubuntu(just substitute ppa:nova-core/release f

Re: [Openstack] Stable and Development Trunks

Just to clear up some issues I've ran into as well...I'm using a deployment script for my internal testing, which leverages 'ppa:nova-core/trunk' so I can access the latest nova-* packages. I know at one time there was 'ppa:nova-core/ppa', and this was considered the 'stable' area for nova-* packa

Re: [Openstack] Stable and Development Trunks

I think this may have to do with confusion over what the release series on Launchpad are... The Bexar series is frozen at this point, and does not get any non-critical bug fixes or feature patches that have been going into the Cactus (trunk) series, unless a post-bexar-release exception is made (n

Re: [Openstack] Stable and Development Trunks

Hi Jason, I think you might wanna check this: http://www.mail-archive.com/nova@lists.launchpad.net/msg00321.html Worth mentioning that the "release" PPA is actually called "release" not "stable" as mentioned in the above mail. I hope this helps. On Thu, Feb 10, 2011 at 7:26 PM, Jason Cannavale

[Openstack] Stable and Development Trunks

All, I'm not sure if this has been discussed before at any length, but I would like to discuss if it makes sense to have source code in the stable trunk and installable packages built and provided from the rapidly changing development trunk. For some background we've been working through some p