There is a proposal to consider a repo as stable if there are no high/critical bugs and there were no such new bugs with this priority for the last 3 days. I'm ok with it.
2014-11-14 17:16 GMT+03:00 Igor Kalnitsky <ikalnit...@mirantis.com>: > Guys, > > The idea of separate unfreezing is cool itself, but we have to define > some rules how to define that fuel-web is stable. I mean, in fuel-web > we have different projects, so when Fuel UI is stable, the > fuel_upgrade or Nailgun may be not. > > - Igor > > On Fri, Nov 14, 2014 at 3:52 PM, Vitaly Kramskikh > <vkramsk...@mirantis.com> wrote: > > 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 > >>> 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 > >> > > > > > > > > -- > > Vitaly Kramskikh, > > Software Engineer, > > Mirantis, Inc. > > > > _______________________________________________ > > 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 > -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
