[openstack-dev] [neutron] neutron-lib impact
bodenvmw at gmail.com
Wed Nov 23 21:45:06 UTC 2016
I would encourage anyone working on neutron-lib related changes to have
a peek at the recently renovated contributing doc  if you haven't
In particular the 'Phase 4: Consume' section  provides some tips on
how we see this workflow playing out.
On 11/23/16 12:39 PM, Armando M. wrote:
> Hi neutrinos,
> In the last few hours a couple of changes landed [1,2] that caused a bit
> of a jam in the neutron subproject gates, as they overlapped with
> another change  having impact on the subprojects.
> This is why it is important to communicate during team meetings and/or
> ML that patches with potential impact are in flight in our review
> pipeline, so that we do our best to coordinate the merge process without
> shooting ourselves in the foot.
> To bring this back to sanity, I issued a temporary revert , so that
>  can land undisturbed. After that, a double revert will be applied,
> once subprojects have had the opportunity to deal with the aftermath of
> the other breaking change [1,2] (e.g. [6,7]).
> From now on, I'd strongly encourage people proposing/reviewing patches
> with potential impact (any impact) to err on the side of caution, and
> take the advised steps to ensure such situations don't happen in the future.
>  https://review.openstack.org/#/c/397704/
>  https://review.openstack.org/#/c/397037/
>  https://review.openstack.org/#/c/386845/
>  https://review.openstack.org/#/c/401377/
>  https://review.openstack.org/#/q/topic:plugin-directory+status:open
>  https://review.openstack.org/#/c/401263/
>  https://review.openstack.org/#/c/401355/
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev