[openstack-dev] [requirements][kolla][openstack-ansible][puppet][tripleo] requirements unfreeze and you, how you should handle it

Alex Schultz aschultz at redhat.com
Thu Feb 8 23:41:22 UTC 2018


On Thu, Feb 8, 2018 at 2:29 PM, Matthew Thode <prometheanfire at gentoo.org> wrote:
> As the title states, cycle trailing projects will need to change their
> requirements update behavior until they create stable/queens branches.
>
> When requirements unfreezes we will be doing rocky work, meaning that
> requirements updates to your projects (our master to your master) will
> be for rocky.
>
> I requests that all the projects tagged in the email's subject get a +1
> from a requirements core before merging until they branch stable/queens.
>

For clarity: before merging requirements updates.  So for TripleO
folks please do not merge any requirements updates unless the
requirements cores have +1'd or we've branched Queens.

> Once they branch stable/queens the projects are free to proceed as
> normal.
>
> If the projects tagged in the subject can ack me (email or irc) I'd
> appreciate it, would give us some peace of mind to unfreeze tomorrow.
>
> --
> Matthew Thode (prometheanfire)
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



More information about the OpenStack-dev mailing list