Excerpts from Dmitry Tantsur's message of 2017-07-29 20:06:18 +0200: > On 07/28/2017 11:13 PM, Doug Hellmann wrote: > > As Thierry mentioned in his countdown email today, the release team has > > now created the stable branches for most deliverables with type > > "library". > > > > We have 3 exceptions: > > > > 1. python-neutronclient had a late release, so I will be branching it > > shortly. > > 2. python-barbicanclient was skipped until they have a chance to resolve > > the critical bug they are working on. > > 3. tempest doesn't branch (we should probably reclassify that as > > something other than a library to avoid issues with the automation) > > > > All libraries should have had updates for the .gitreview file in the new > > branch, the constraints URL in the tox.ini file, and the reno > > configuration (in master, if the project uses reno). > > > > Landing any of the patches in the stable/pike branch will trigger a new > > documentation build publishing to docs.o.o/$project/pike. > > > > Please take over any of the bot-created patches that do not pass your > > validation jobs and fix them so that they can land as soon as possible. > > Just to clarify: we cannot land the tox.ini change until the requirements > repo > is actually branched, right?
Good point. The tests for those patches are passing for some projects in CI, but when the patches are landed it will make it a little harder for anyone to run the tests for the branch elsewhere because the requirements repo has not yet been branched. So, yes, hold off on landing the constraint URL changes. Doug __________________________________________________________________________ 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
