Evgeniy, That means that the stable branch can be created for some repos earlier. For example, fuel-web repo seems not to have critical issues for now and I'd like master branch of that repo to be opened for merging various stuff which shouldn't go to 6.0 and do not wait until all other repos stabilize.
2014-11-14 16:42 GMT+03:00 Evgeniy L <e...@mirantis.com>: > 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 <vkramsk...@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 >> OpenStackfirstname.lastname@example.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc.
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev