From: Paul I. <piv...@gm...> - 2011-11-03 21:21:30
|
Hey gang, as per this discussion: On Thu, Nov 3, 2011 at 3:40 AM, John Hunter <jd...@gm...> wrote: > On Nov 2, 2011, at 10:47 PM, Benjamin Root <ben...@ou...> wrote: > > So the instruction should be to remind John Hunter to update the entry in > PyPi? Got it. > > > Even better, it should be: > 1) update the release notes in the devel docs > 2) give Ben access to the pypi acct. I added a note to the release docs about tagging the releases - right now, there's no clear way inside git to know what ended up in v1.1.0 final, without grabbing a tarball and poking around. I'm inlining the relevant part of that commit here, so that John/Ben can tag the release after the fact. --- For each release candidate as well as for the final release version, please `git tag` the commit you will use for packaging like so:: git tag -a v1.1.0rc1 The `-a` flag will allow you to write a message about the tag, and affiliate your name with it. A reasonable tag message would be something like ``v1.1.0 Release Candidate 1 (September 24, 2011)``. To tag a release after the fact, just track down the commit hash, and:: git tag -a v1.0.1 a9f3f3a50745 Tags allow developers to quickly checkout different releases by name, and also provides source download via zip and tarball on github. --- best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 |