Thanks Andrew. Team, if there are any disagreements - let's discuss it. Otherwise, I think we should be just strict and follow defined process. We can deliver high priority bugfixes in updates channel later if needed.
I hope that reasoning is clear for everything. Every bugfix has a potential to break something. It's basically a risk. On Mon, Sep 14, 2015 at 8:57 AM Andrew Maksimov <amaksi...@mirantis.com> wrote: > Hi Everyone! > > I would like to reiterate the bugfix process after Hard Code Freeze. > According to our HCF definition [1] we should only merge fixes for > *Critical* bugs to *stable/7.0* branch, High and lower priority bugs > should NOT be accepted to *stable/7.0* branch anymore. > Also we should accept patches for critical bugs to *stable/7.0* branch > only after the corresponding patchset with same ChangeID was accepted into > master. > > [1] - https://wiki.openstack.org/wiki/Fuel/Hard_Code_Freeze > > Regards, > Andrey Maximov > Fuel Project Manager > __________________________________________________________________________ > 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 > -- Mike Scherbakov #mihgen
__________________________________________________________________________ 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
