Menu
▾
▴
matplotlib-devel
|
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
|
|
From: Paul I. <piv...@gm...> - 2011-11-10 23:52:07
|
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 <piv...@gm...> 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 |
|
From: Benjamin R. <ben...@ou...> - 2011-11-12 01:20:11
|
On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote: > 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? > > Sure thing. I will add that tag. Ben Root |
|
From: Benjamin R. <ben...@ou...> - 2011-11-12 01:40:49
|
On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote: > On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote: > >> 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? >> >> > Sure thing. I will add that tag. > > Ben Root > > The best I can figure is that commit 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the release announcement by John on Oct. 11. There was subsequently a commit on that day to fix ipython links. I can't remember if that happened before or after (I think after). Can anybody concur? Ben Root |
|
From: Paul I. <piv...@gm...> - 2011-11-12 07:47:56
|
On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root <ben...@ou...> wrote: > On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote: >> >> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote: >>> >>> 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? >>> >> >> Sure thing. I will add that tag. >> >> Ben Root >> > > The best I can figure is that commit > 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the release > announcement by John on Oct. 11. There was subsequently a commit on that > day to fix ipython links. I can't remember if that happened before or after > (I think after). > > Can anybody concur? On my PR to fix those links, John closed it and said he'd add it to the release branch, and they're up on the site, so I'd say that commit made it in. But I don't know if there were others afterward that made it in -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 |
|
From: John H. <jd...@gm...> - 2011-11-12 12:57:05
|
On Nov 12, 2011, at 2:47 AM, Paul Ivanov <piv...@gm...> wrote: > On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root <ben...@ou...> wrote: >> On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote: >>> >>> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote: >>>> >>>> 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? >>>> >>> >>> Sure thing. I will add that tag. >>> >>> Ben Root >>> >> >> The best I can figure is that commit >> 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the release >> announcement by John on Oct. 11. There was subsequently a commit on that >> day to fix ipython links. I can't remember if that happened before or after >> (I think after). >> >> Can anybody concur? > > On my PR to fix those links, John closed it and said he'd add it to > the release branch, and they're up on the site, so I'd say that commit > made it in. But I don't know if there were others afterward that made > it in > My memory is that the ipy pull request came just after the tarball, so I think you have it right Ben > |
|
From: Benjamin R. <ben...@ou...> - 2011-11-14 15:39:52
|
On Sat, Nov 12, 2011 at 6:56 AM, John Hunter <jd...@gm...> wrote: > > > On Nov 12, 2011, at 2:47 AM, Paul Ivanov <piv...@gm...> wrote: > > > On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root <ben...@ou...> wrote: > >> On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote: > >>> > >>> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> > wrote: > >>>> > >>>> 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? > >>>> > >>> > >>> Sure thing. I will add that tag. > >>> > >>> Ben Root > >>> > >> > >> The best I can figure is that commit > >> 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the > release > >> announcement by John on Oct. 11. There was subsequently a commit on > that > >> day to fix ipython links. I can't remember if that happened before or > after > >> (I think after). > >> > >> Can anybody concur? > > > > On my PR to fix those links, John closed it and said he'd add it to > > the release branch, and they're up on the site, so I'd say that commit > > made it in. But I don't know if there were others afterward that made > > it in > > > > > My memory is that the ipy pull request came just after the tarball, so I > think you have it right Ben > > Done! Ben Root |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X