openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #06032
Re: Providing packages for stable releases of OpenStack
I'm ok with everything so far, but from "
http://wiki.openstack.org/StableBranch":
*"The stable branch will only be maintained until the next release is out.
This period may be extended if there are volunteers to maintain it beyond
this point."*
With a 6 months release cycles, it still looks a sort period of time for a
production deployment, and some people/companies can not relay on those
volunteers to appear to maintain it for more time.
Is there any plan (or can be proposed) to have some kind of LTS
release? I've read some place that essex + Ubuntu 12.04 LTS can be a good
candidate; essex is considered the first "production ready" release, but it
will not have quantum, we are tying openstack within an specific
distribution... Anyway, (ubuntu12.04 + essex)^LTS looks great, and we have
time to discuss what to do for a future "LTS" release.
Ghe Rivero
On Thu, Dec 8, 2011 at 5:59 PM, Duncan McGreggor <duncan@xxxxxxxxxxxxx>
wrote:
>
> On 07 Dec 2011 - 08:15, Mark McLoughlin wrote:
> > On Tue, 2011-12-06 at 14:12 -0800, Duncan McGreggor wrote:
> > > On 06 Dec 2011 - 13:52, Duncan McGreggor wrote:
> > > > On 06 Dec 2011 - 21:14, Thierry Carrez wrote:
> > > > > Tim Bell wrote:
> > > > > > I'm not clear on who will be maintaining the stable/diablo
branch.
> > > > > > The people such as EPEL for RedHat systems need to have
something
> > > > > > with the appropriate bug fixes back ported.
> > > > > >
> > > > > > There are an increasing number of sites looking to deploy in
> > > > > > production and cannot follow the latest development version.
> > > > >
> > > > > Agreed on the need, we discussed this at length during the design
> > > > > summit. The stable branches have been established and are
maintained by
> > > > > the "OpenStack Stable Branch Maintainers" team. Currently this
team is
> > > > > mostly made of distribution members (Ubuntu and Fedora/RedHat,
mostly)
> > > > > collaborating on a single branch to avoid duplication of effort.
> > > > >
> > > > > See:
> > > > > https://launchpad.net/~openstack-stable-maint
> > > > > http://wiki.openstack.org/StableBranch
> > > >
> > > > Okay, I think this mostly addresses item #4 that I wanted to add to
your
> > > > summary, Thierry.
> > > >
> > > > I do have the following minor concerns, though:
> > > >
> > > > * that wiki page's summary (intro sentence) only specifically
mentions
> > > > Diablo; I'd like to see something along the lines of "currently
> > > > focusing on Diablo. If these processes evolve into a successful
> > > > model, they will be applied to all future releases."
> >
> > Added.
> >
> > > > * the discussion on the page treats this as an experiment (this is
> > > > good!), but I'd like to see a phrase alone the lines of "if this
> > > > experiment is successful, we will do X to ensure these processes
> > > > become an official part of the workflow."
> >
> > Cleaned up the "this is an experiment" text a bit, it's gone beyond an
> > experiment now I think.
>
> Very cool, Mark! Thanks so much!!
>
> d
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
--
.''`. Pienso, Luego Incordio
: :' :
`. `'
`- www.debian.org
GPG Key: 26F020F7
GPG fingerprint: 4986 39DA D152 050B 4699 9A71 66DB 5A36 26F0 20F7
Follow ups
References