Open Stack

Excerpts from Ivan Kolodyazhny's message of 2015-09-28 17:41:46 +0300:
> Hi Thierry,
> 
> Thank you for sharing this information with us so early. One
> comment/question from me about FinalClientLibraryRelease:
> 
> Could we make client release at least one week later after M-3 milestone?
> It will give us more chances to have features landed into the client if
> they were merged late before M-3 and feature freeze.

The timeline in this schedule is more or less the same as what we've
done the past two cycles.  Allowing client feature work to carry
on longer in the schedule does not leave time for dealing with
issues introduced by buggy client releases.

I recommend prioritizing features that are going to require work
in the clients so those patches can land early enough to follow the
schedule, especially if those are features that other projects are
going to be depending on.

Doug

> 
> Regards,
> Ivan Kolodyazhny
> 
> On Mon, Sep 28, 2015 at 5:08 PM, Thierry Carrez <thierry at openstack.org>
> wrote:
> 
> > Hi everyone,
> >
> > You can find the proposed release schedule for Mitaka here:
> >
> > https://wiki.openstack.org/wiki/Mitaka_Release_Schedule
> >
> > That places the end release on April 7, 2016. It's also worth noting
> > that in an effort to maximize development time, this schedule reduces
> > the time between Feature Freeze and final release by one week (5 weeks
> > instead of 6 weeks). That means we'll collectively have to be a lot
> > stricter on Feature freeze exceptions this time around. Be prepared for
> > that.
> >
> > Feel free to ping the Release management team members on
> > #openstack-relmgr-office if you have any question.
> >
> > --
> > Thierry Carrez (ttx)
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >