Folks

First of all, there is a critical bug which is not fixed.  It may be
floating because it is related to implicit resources ordering in puppet.
But it does not mean that it is not a merge blocker.

Secondly, I do not share your optimism about easiness of bugfixing of
possible regressions because I do not see results of more complete testing
of such changes.

Additionally, there was no preliminary discussion about this change. You
did not give us enough time to express our opinion. For example, the
original email was sent after 8pm msk and I had already left the office.

Finally goes my constructive proposal.

1) merge the fix https://review.openstack.org/281440
2) get several consecutive green bvts
3) in meantime drag this mitaka iso through swarm
4) compare the results and merge mitaka iso on Saturday if no criticals are
found. Saturday is a working day in Russia, so there will be low dev
activity and we will be able to control the swarm run.
17 февр. 2016 г. 21:06 пользователь "Igor Kalnitsky" <
ikalnit...@mirantis.com> написал:

> Vladimir,
>
> Obviously, there will be regressions in other scenarios. However, it's
> better to catch them now. We have not much time before FF, and it'd be
> better to merge such features as early as possible, and do not wait
> for merge hell a day before FF.
>
> The thing we need to know is that BVT is green, and that means most
> developers aren't blocked.
>
> Thanks,
> Igor
>
> On Wed, Feb 17, 2016 at 7:48 PM, Vladimir Kuklin <vkuk...@mirantis.com>
> wrote:
> > Fuelers
> >
> > I have strong opinion against this merge freeze right now. We have
> critical
> > bugs blocking bvt and we do not have enough info on mitaka readiness for
> > other scenarios than bvt.
> >
> > 17 февр. 2016 г. 20:45 пользователь "Dmitry Borodaenko"
> > <dborodae...@mirantis.com> написал:
> >
> >> Fuel core reviewers,
> >>
> >> Fuel CI is being migrated to an ISO image with Mitaka packages, please
> >> don't merge any commits to any Fuel repositories without coordination
> >> with Aleksandra until further notice.
> >>
> >> This merge freeze is expected to last a few hours.
> >>
> >> --
> >> Dmitry Borodaenko
> >>
> >>
> __________________________________________________________________________
> >> 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
>
__________________________________________________________________________
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

Reply via email to