Just wanted to re-ping the list, but include John and Ben directly: can we get the appropriate commit tagged as v1.1.0 in the git repo?
On Thu, Nov 3, 2011 at 2:21 PM, Paul Ivanov <pivanov...@gmail.com> wrote: > 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 ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
