We probably should promote all of the 'major' tags to release + get DOIs
for all of the old releases.
I can take care of this, but if someone wants to beat me to it, please do :)
tom
On Wed Nov 05 2014 at 11:32:13 AM Jens Nielsen
wrote:
> That makes sense. I would consider deleting "1.3.1" wh
That makes sense. I would consider deleting "1.3.1" which is the same
commit as "v1.3.1"
@Benjamin Github allows highlighting releases at
https://github.com/matplotlib/matplotlib/releases which have release notes.
Perhaps we should add release notes for releases before 1.4.0 from the
change log to
Same here. I like the old tags for historical research purposes. Now, if
there was a way for github to only display the N most recent tags, I would
go for that...
On Wed, Nov 5, 2014 at 10:32 AM, Thomas Caswell wrote:
> I am -1 on removing old tags. The _point_ of tags is they don't move.
>
> I
I am -1 on removing old tags. The _point_ of tags is they don't move.
IPython is a younger project, moving much faster, and have an interest in
keeping everyone close to the bleeding edge, we don't have that luxury.
For a long time debian shipped an rc (1.3.1rc1 iirc) so there is evidence
of peop
I removed the rgb2lab_local branch now (I decided that this is not the way
to go and I have a local copy in my own remote of this). On a related note
should be consider removing tags for old release candidates? I know that
IPython does this and it does clean up the tags quite a bit since
approximat
