Hi Mike and Igor, Thank you for the opinions.
We already talked to Matt and he is fine with Fuel Menu commit. We will target the changes for Tuesday and will work with reviewers and Mos-Linux team to have blocker bug resolved and commits merged. Thanks, Dmitry. On Fri, Dec 4, 2015 at 2:04 PM, Igor Kalnitsky <ikalnit...@mirantis.com> wrote: > Hey Dmitry, > > I'm ok with FFE till Tuesday. Moreover, it makes sense to do so in > order to reduce affection on CentOS 7 patches. > > - Igor > > On Thu, Dec 3, 2015 at 8:58 PM, Dmitry Klenov <dkle...@mirantis.com> > wrote: > > Hi folks, > > > > Let me clarify the situation with Ubuntu bootstrap feature. > > > > First of all, I would like to highlight that all functional commits for > this > > feature were merged. This means that starting from yesterday everyone > has an > > ability to switch to Ubuntu-based bootstrap manually and start using it. > So > > I do not see the risk in loosing testing cycles in the community. > > > > The item which brought concerns on today status meeting was the > enablement > > of the feature by default. To do it, 2 patches have to be merged > together: > > * https://review.openstack.org/#/c/250662/ - main switch. > > * https://review.openstack.org/#/c/251908/ - compatibility commit to QA > > suite to comply with new bootstrap config format. > > > > I would like to raise the question if we can have a feature freeze > exception > > for these 2 patches? > > > > There are a couple of reasons why I consider it safer to merge these > patches > > several days later: > > * There is a bug caught today which will block the tests to pass if we > > switch to Ubuntu bootstrap by default: > > https://bugs.launchpad.net/fuel/+bug/1522406 > > * There were concerns that a lot of FF commit merges can bring > instability > > to QA suite. So it might be reasonable not to bring one more variable > right > > now and to enable ubuntu bootstrap by default when all automated tests > are > > stabilized. > > > > I would like to ask engineering and QA leads to express their ideas on > this. > > > > Thanks, > > Dmitry. > > > > > __________________________________________________________________________ > > 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 > > > > __________________________________________________________________________ > 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 >
__________________________________________________________________________ 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
