[openstack-dev] [Fuel] Separate code freeze for repos

Evgeniy L eli at mirantis.com
Fri Nov 14 13:42:44 UTC 2014


Hi,

>> There was an idea to make a separate code freeze for repos

Could you please clarify what do you mean?

I think we should have a way to merge patches for the next
release event if it's code freeze for the current.

Thanks,

On Tue, Nov 11, 2014 at 2:16 PM, Vitaly Kramskikh <vkramskikh at mirantis.com>
wrote:

> Folks,
>
> There was an idea to make a separate code freeze for repos, but we decided
> not to do it. Do we plan to try it this time? It is really painful to
> maintain multi-level tree of dependent review requests and wait for a few
> weeks until we can merge new stuff in master.
>
> --
> Vitaly Kramskikh,
> Software Engineer,
> Mirantis, Inc.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141114/08a746ee/attachment.html>


More information about the OpenStack-dev mailing list