Excerpts from Robert Collins's message of 2015-12-04 09:13:26 +1300: > On 28 November 2015 at 03:32, Doug Hellmann <[email protected]> wrote: > > Next week (Dec 1-3) is the Mitaka 1 milestone deadline. Release > > liaisons for all managed projects using the cycle-with-milestones > > release model will need to propose tags for their repositories by > > Thursday. Tag requests submitted after Dec 3 will be rejected. > ... > > 3. Prepare a patch to the project repository removing the version > > line from setup.cfg. > > > > Set the patch to depend on the release patch from step 1, and > > use the topic "remove-version-from-setup". > > There is a gotchya here that may confuse people. The patch in step 3, > if prepared concurrently with the tag, will show versions regressing, > but in the gate it will do the right thing! > > The issue is merely that if the local git revision doesn't reach the > tag, then as far pbr is concerned (and git describe), the new tag > doesn't exist, and so its like step 2 was skipped. So - to avoid > confusing anyone, make sure you base the patch for step 3 on top of > the revision being tagged in step 2. >
Thanks for pointing that out, Robert. Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
