Thanks Deepak!
Mike is also sending the announce to the vendors in the mail accounts listed in the CI Status page[1]. [1] https://wiki.openstack.org/wiki/Cinder/third-party-ci-status On Tue, Jan 20, 2015 at 6:47 AM, Deepak Shetty <dpkshe...@gmail.com> wrote: > Yuck ! its Mar. 19, 2015 (bad copy paste before) > > On Tue, Jan 20, 2015 at 12:16 PM, Deepak Shetty <dpkshe...@gmail.com> > wrote: > >> Just so that people following this thread know about the final decision, >> Per >> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines >> the deadline for CI is extended to Mar. 3, 2015 for all volume drivers. >> >> <snip> >> Deadlines >> >> All volume drivers >> <https://github.com/openstack/cinder/tree/master/cinder/volume/drivers> >> need to have a CI by end of* K-3, March 19th 2015*.* Failure will result >> in removal in the Kilo release.* Discussion regarding this was in the >> #openstack-meeting IRC room during the Cinder meeting. Read discussion >> logs >> <http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-14-16.00.log.html#l-21> >> >> </snip> >> >> On Tue, Jan 13, 2015 at 3:55 AM, Mike Perez <thin...@gmail.com> wrote: >> >>> On 09:03 Mon 12 Jan , Erlon Cruz wrote: >>> > Hi guys, >>> > >>> > Thanks for answering my questions. I have 2 points: >>> > >>> > 1 - This (remove drivers without CI) is a way impacting change to be >>> > implemented without exhausting notification and discussion on the >>> mailing >>> > list. I myself was in the meeting but this decision wasn't crystal >>> clear. >>> > There must be other driver maintainers completely unaware of this. >>> >>> I agree that the mailing list has not been exhausted, however, just >>> reaching >>> out to the mailing list is not good enough. My instructions back in >>> November >>> 19th [1][2] were that we need to email individual maintainers and the >>> openstack-dev list. That was not done. As far as I'm concerned, we can't >>> stick >>> to the current deadline for existing drivers. I will bring this up in >>> the next >>> Cinder meeting. >>> >>> > 2 - Build a CI infrastructure and have people to maintain a the CI for >>> a >>> > new driver in a 5 weeks frame. Not all companies has the knowledge and >>> > resources necessary to this in such sort period. We should consider a >>> grace >>> > release period, i.e. drivers entering on K, have until L to implement >>> > theirs CIs. >>> >>> New driver maintainers have until March 19th. [3] That's around 17 weeks >>> since >>> we discussed this in November [2]. This is part the documentation for >>> how to >>> contribute a driver [4], which links to the third party requirement >>> deadline >>> [3]. >>> >>> [1] - >>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html >>> [2] - >>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34 >>> [3] - >>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines >>> [4] - https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver >>> >>> -- >>> Mike Perez >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
