Re: [openstack-dev] [cinder driver] A question about Kilo merge point

2014-12-17 Thread Mike Perez 
On 11:40 Tue 16 Dec , liuxinguo wrote:
> If a cinder driver can not be mergerd into Kilo before Kilo-1, does it means 
> that this driver will has very little chance to be merged into Kilo?
> And what percentage of drivers will be merged before Kilo-1 according to the 
> whole drivers that will be merged into Kilo at last?
> 
> Thanks!

All the details for this is here:

http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html

-- 
Mike Perez

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder driver] A question about Kilo merge point

2014-12-17 Thread Erlon Cruz 
Hi,

Yes, I think that the changes of being merged after K1 are few. Check this
docs with the priority list that the core team are working on:

https://etherpad.openstack.org/p/cinder-kilo-priorities

Erlon

On Tue, Dec 16, 2014 at 9:40 AM, liuxinguo  wrote:
>
>  If a cinder driver can not be mergerd into Kilo before Kilo-1, does it
> means that this driver will has very little chance to be merged into Kilo?
>
> And what percentage of drivers will be merged before Kilo-1 according to
> the whole drivers that will be merged into Kilo at last?
>
>
>
> Thanks!
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev