Hi,

This weekend our driver [https://review.openstack.org/#/c/130733/] got a -2
stating that "This is past the deadline for release of new drivers in
Kilo." and "the deadline for new drivers passed at the end of Kilo-1. This
needs to wait for the L release."

But, in another mail on the mailing list we were informed:
"
If your driver is submitted *LATE* in k-1, and meets *all* the items above,
but isn't merged, it will be still be considered for merge in k-2 or k-3.
"
The items above being that the blueprint is submitted, together with cert
tests and the code is submitted to gerrit and that a CI is working.

We had the blueprint, cert tests and code on gerrit *EARLY* in k-1 (first
patchset was on Oct 24), blueprint was approved for k-1 and cert tests were
posted.
CI is under construction, and will be ready by March deadline.


So, can someone from cinder core clarify why the driver is delayed to L
when all items are met?

Thanks,
Eduard
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__________________________________________________________________________
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

Reply via email to