Menu
▾
▴
matplotlib-devel
|
From: Thomas C. <tca...@gm...> - 2014-11-01 15:49:12
|
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 |
|
From: Todd <tod...@gm...> - 2014-11-01 16:14:08
|
On Nov 1, 2014 4:49 PM, "Thomas Caswell" <tca...@gm...> 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. |
|
From: Thomas C. <tca...@gm...> - 2014-11-01 16:23:42
|
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 <tod...@gm...> wrote: > > On Nov 1, 2014 4:49 PM, "Thomas Caswell" <tca...@gm...> 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 > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Joel B. M. <jo...@ki...> - 2014-11-01 16:31:49
|
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 |
|
From: Benjamin R. <ben...@ou...> - 2014-11-01 17:49:36
|
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 <jo...@ki...> 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 > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Eric F. <ef...@ha...> - 2014-11-01 18:31:51
|
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 |
|
From: Thomas C. <tca...@gm...> - 2014-11-01 19:56:44
|
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 <ef...@ha...> 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 > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Jens N. <jen...@gm...> - 2014-11-05 15:00:46
|
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 On Sat, Nov 1, 2014 at 7:56 PM, Thomas Caswell <tca...@gm...> 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 <ef...@ha...> 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#issuecomm >> ent-61372162). >> > >> > Tom >> >> Seems to me like a good idea. >> >> Eric >> >> >> ------------------------------------------------------------ >> ------------------ >> _______________________________________________ >> Matplotlib-devel mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
×
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