[openstack-dev] [oslo][release] oslo freeze this week?
Doug Hellmann
doug at doughellmann.com
Mon Aug 24 20:04:18 UTC 2015
Excerpts from Kuvaja, Erno's message of 2015-08-24 17:12:58 +0000:
> > -----Original Message-----
> > From: Thierry Carrez [mailto:thierry at openstack.org]
> > Sent: Monday, August 24, 2015 1:47 PM
> > To: openstack-dev at lists.openstack.org
> > Subject: Re: [openstack-dev] [oslo][release] oslo freeze this week?
> >
> > On Aug 23, 2015, at 5:51 PM, Robert Collins <robertc at robertcollins.net>
> > wrote:
> > > On 24 August 2015 at 09:28, Doug Hellmann <doug at doughellmann.com>
> > wrote:
> > >> I have marked on my version of the release schedule that we will have
> > the Oslo libraries frozen this week. Are we still planning to do that? We
> > should figure out what that means as far as creating stable branches and
> > version caps and all of those things that caused us so much trouble last cycle.
> > >
> > > We're not capping anything. We're depending on constraints to carry us
> > > forward. The constraints for tox stuff works but isn't widely
> > > deployed: it is partly waiting on a governance change... I think we
> > > should use this as a forcing function for projects to opt-in to that.
> > > grenade uses constraints so only stable branches should be affected by
> > > that.
> >
> > Back in YVR we had the following process drafted on a whiteboard:
> >
> > 1. Enable master->stable cross-check
> > 2. Release Oslo, make stable branches for Oslo
> > 2.1 Converge constraints
> > 3. liberty-3 / FF / soft requirements freeze 4. hard requirements freeze 5.
> > RC1 / make stable branches for services 6. Branch requirements, disable
> > cross-check 7. Unfreeze requirements
> >
> > Is there anything new that makes this proposed process invalid ?
> >
> > If not, since (3) is Thursday next week, that means we need to cover the first
> > 3 items in the coming week ?
> >
> > --
> > Thierry Carrez (ttx)
> >
>
> That does sound absolutely reasonable.
>
> I'd like to add/ask where in there we have the last point to cut rest of the libs? That should probably happen by 3. As well?
Except for clients the other libraries usually affect fewer projects,
so it's probably OK for those to slip a bit -- especially now that
we have the constraints system in place to detect issues with
releases, and we can block them without bringing the gate to a halt.
That said, it would be good if they could have a final feature
release this week, too.
Doug
>
> - Erno
>
More information about the OpenStack-dev
mailing list