openstack team mailing list archive

[Jay Pipes <jaypipes@xxxxxxxxx>]

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 (none have been yet, AFAIK).

So, if you pull lp:glance/bexar, you won't see ANY of the commits that
have been going into trunk since the 3rd of February.

lp:glance == the latest trunk series (Cactus right now) and contains
all fixes, features and patches that have been merged since after
Bexar was released.

I think it's just the case that you have been using lp:glance thinking
it is the stable release series. It isn't. lp:glance/bexar is.

Cheers!
jay

On Thu, Feb 10, 2011 at 12:26 PM, Jason Cannavale <jason@xxxxxxxxxxxxx> wrote:
> 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 proof of concept
> deployments. Because the packages are coming from the development trunk we
> have been bitten repeatedly by having packages updated following code merges
> throughout the day. This has resulted in services such as networking no
> longer functioning. It seems to me, at least, that it would make sense to
> have a set of known working packages, packaged at each release point, in the
> stable trunk and having the source to build from in the development trunk.
>
> Thoughts?
>
> Jason
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>