openstack team mailing list archive

[John Griffith <john.griffith@xxxxxxxxxxxxx>]

On Sat, Feb 2, 2013 at 9:49 AM, Thierry Carrez <thierry@xxxxxxxxxxxxx>wrote:

> Xiazhihui (Hashui, IT) wrote:
> > 1.I want to know if grizzly-3 is the last of Grizzly? Will it have a
> > grizzly-4?
>
> No there won't be another milestone. The release schedule appears at:
> http://wiki.openstack.org/GrizzlyReleaseSchedule
>
> The release cycle is explained at:
> http://wiki.openstack.org/ReleaseCycle
>
> The developer section of this page contains a few other useful pointers:
> http://wiki.openstack.org/HowToContribute
>
> > 2.I hava a cinder driver, if I want to commit it in grizzly-3. What's
> > the deadline of the codes committing? Should the code be approved by PTL
> > before 2013-02-21 ?
>
> The proposed change needs to be merged before the end of the day on
> February 19 (when we branch for grizzly-3 delivery). That means
> gathering necessary code review approvals before then. This can take
> time, so code should be submitted asap.
>
> > 3.Grizzly will public in April 2013, can I commit my blueprint codes
> > from 2013-02-21 to April 2013?
>
> No, Feb 19 is Feature Freeze, so if you don' tmake it by then, your
> feature will be part of the next release (Havana) instead.
>
> Engaging early with the developer community (and the project PTL) is the
> key to success. Ideally features would be presented to the design summit
> and implemented in the months after, to be integrated in the release at
> the end of the 6-month cycle.
>
> Regards,
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
In addition to everything that Thierry pointed out, I'd also like to
mention that Cinder is a bit unique.  Cinder is a bit different than other
projects because there's a constant flow of vendors wishing to implement
new drivers.  The result is we typically get to the final week or two of
the last feature milestone in a release cycle and suddenly half a dozen new
blue-prints for drivers are submitted.  This makes for a very troubling
week of trying to get reviews, tests etc while still getting all the
*normal* back-log of things in.

We're planning to have a session at the summit to agree upon and formalize
some policies around driver submissions.  Of course we still want to
encourage folks to contribute and participate, we just want to avoid the
trend of everything showing up in the last week of the milestone if
possible.

If you want to get a driver added to Cinder in time for Grizzly, please get
a BP submitted and get the patch in as soon as possible (ideally early this
coming week).  Also feel free to grab me on IRC and we can talk more about
where you're at and how we can make this happen for the Grizzly release.

Thanks,
John