[matplotlib-devel] remove old branches

2014-11-01 Thread Thomas Caswell
Does anyone protest to removing all of the branches from the main repo
except:

 - master
 - v1.4.x
 - v1.4.2-doc

Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).

Tom
--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] remove old branches

2014-11-01 Thread Todd
On Nov 1, 2014 4:49 PM, "Thomas Caswell"  wrote:
>
> Does anyone protest to removing all of the branches from the main repo
except:
>
>  - master
>  - v1.4.x
>  - v1.4.2-doc
>
> Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
>
> Tom

What about having a "matplotlib/matplotlib-archive" fork where old branches
and tags can be kept?  That way someone can always go back and install an
old version if they really need to.
--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] remove old branches

2014-11-01 Thread Thomas Caswell
Todd,

The tags would not go anywhere, just the branches would be removed.

The tags are for releases, branches are for active work and there should be
no active work on anything but those three branches.

Tom

On Sat, Nov 1, 2014, 12:14 Todd  wrote:

>
> On Nov 1, 2014 4:49 PM, "Thomas Caswell"  wrote:
> >
> > Does anyone protest to removing all of the branches from the main repo
> except:
> >
> >  - master
> >  - v1.4.x
> >  - v1.4.2-doc
> >
> > Having old branches around can lead to confusion (see
> https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
> >
> > Tom
>
> What about having a "matplotlib/matplotlib-archive" fork where old
> branches and tags can be kept?  That way someone can always go back and
> install an old version if they really need to.
> 
> --
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] remove old branches

2014-11-01 Thread Joel B. Mohler
On 11/01/2014 11:49 AM, Thomas Caswell wrote:
> Does anyone protest to removing all of the branches from the main repo 
> except:
>
>  - master
>  - v1.4.x
>  - v1.4.2-doc
>

As a person who was distracted by too many branches in that list, I 
fully support this.

Joel

--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] remove old branches

2014-11-01 Thread Benjamin Root
I think this is reasonable. If anything, I *might* want to keep N+1
branches, but that might be too much.

On Sat, Nov 1, 2014 at 12:31 PM, Joel B. Mohler 
wrote:

> On 11/01/2014 11:49 AM, Thomas Caswell wrote:
> > Does anyone protest to removing all of the branches from the main repo
> > except:
> >
> >  - master
> >  - v1.4.x
> >  - v1.4.2-doc
> >
>
> As a person who was distracted by too many branches in that list, I
> fully support this.
>
> Joel
>
>
> --
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] remove old branches

2014-11-01 Thread Eric Firing
On 2014/11/01, 5:49 AM, Thomas Caswell wrote:
> Does anyone protest to removing all of the branches from the main repo
> except:
>
>   - master
>   - v1.4.x
>   - v1.4.2-doc
>
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] remove old branches

2014-11-01 Thread Thomas Caswell
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  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:
> >
> >   - master
> >   - v1.4.x
> >   - v1.4.2-doc
> >
> > 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel