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 people in the wild caring about arbitrary tags.
Tom
···
On Sat, Nov 1, 2014 at 7:56 PM, Thomas Caswell <tcaswell@…149…> wrote:
This is done now. All of the branches were fully merged except for v1.1.x which had a single line change to contents.rst which ended up on the main branch through other means.
I have local branches pointing to all of the removed branches so if there is panic about their removal and everyone runs a prune command on the upstream repos we still have this information around.
I left rgb2lab_local because there is still an open PR against it, but will go away when we close that PR.
Tom
On Sat Nov 01 2014 at 2:32:19 PM Eric Firing <efiring@…229…> wrote:
On 2014/11/01, 5:49 AM, Thomas Caswell wrote:
Does anyone protest to removing all of the branches from the main repo
except:
Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
Tom
Seems to me like a good idea.
Eric
Matplotlib-devel mailing list
Matplotlib-devel@…1041…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
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 <tcaswell@…149…> wrote:
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 people in the wild caring about arbitrary tags.
Tom
On Wed Nov 05 2014 at 10:01:51 AM Jens Nielsen <jenshnielsen@…149…> wrote:
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 approximately half the tags are for release candidates.
Jens
Matplotlib-devel mailing list
Matplotlib-devel@…1041…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
On Sat, Nov 1, 2014 at 7:56 PM, Thomas Caswell <tcaswell@…149…> wrote:
This is done now. All of the branches were fully merged except for v1.1.x which had a single line change to contents.rst which ended up on the main branch through other means.
I have local branches pointing to all of the removed branches so if there is panic about their removal and everyone runs a prune command on the upstream repos we still have this information around.
I left rgb2lab_local because there is still an open PR against it, but will go away when we close that PR.
Tom
On Sat Nov 01 2014 at 2:32:19 PM Eric Firing <efiring@…229…> wrote:
On 2014/11/01, 5:49 AM, Thomas Caswell wrote:
Does anyone protest to removing all of the branches from the main repo
except:
Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
Tom
Seems to me like a good idea.
Eric
Matplotlib-devel mailing list
Matplotlib-devel@…1041…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
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 separate them from the release candidates.
Jens
···
On Wed, Nov 5, 2014 at 4:15 PM, Benjamin Root <ben.root@…867…> wrote:
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 <tcaswell@…149…> wrote:
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 people in the wild caring about arbitrary tags.
Tom
On Wed Nov 05 2014 at 10:01:51 AM Jens Nielsen <jenshnielsen@…149…> wrote:
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 approximately half the tags are for release candidates.
Jens
Matplotlib-devel mailing list
Matplotlib-devel@…1041…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
On Sat, Nov 1, 2014 at 7:56 PM, Thomas Caswell <tcaswell@…149…> wrote:
This is done now. All of the branches were fully merged except for v1.1.x which had a single line change to contents.rst which ended up on the main branch through other means.
I have local branches pointing to all of the removed branches so if there is panic about their removal and everyone runs a prune command on the upstream repos we still have this information around.
I left rgb2lab_local because there is still an open PR against it, but will go away when we close that PR.
Tom
On Sat Nov 01 2014 at 2:32:19 PM Eric Firing <efiring@…229…> wrote:
On 2014/11/01, 5:49 AM, Thomas Caswell wrote:
Does anyone protest to removing all of the branches from the main repo
except:
Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
Tom
Seems to me like a good idea.
Eric
Matplotlib-devel mailing list
Matplotlib-devel@…1041…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel