John et al., (At the moment I can't compile the branch--I just sent Mike a message about that off the list, with voluminous output.)
It seems like what is needed is not exactly a merge operation but simply a renaming of the trunk and the branch. Maybe some doc files need to be merged, but that is about it. Correct? In any case, I will be happy to see the move take place, and I think we already agreed that this is a good time to do it. All this brings to mind the discussion taking place over the last week on the numpy list regarding switching from svn to bzr or hg. http://thread.gmane.org/gmane.comp.python.numeric.general/18130 (I have been using hg locally for a couple years, and I like it.) The motivation is the greater ease of branching and merging with distributed VCS systems in comparison to SVN. In the numpy list discussion, it sounds like all participants except Travis favor making the switch. For us to make such a change would require switching the repo host from sourceforge to something else--I suspect Enthought would be happy to host us. Apart from the initial effort and spinup required--and I don't mean to dismiss that as trivial--I think that using a suitable DVCS would facilitate progress with mpl. If so, is it crazy to do it as part of a major branch/trunk switch, or does that perhaps make it easier? Comments? Eric John Hunter wrote: > Now that the 0.91.2 release is out, I am inclined to merge Michael's > transforms branch into the trunk. Since many people rely on svn, we > probably need to advertise this move broadly, with a news item on the > web page and announcements on the mailing lists, with instructions on > how to checkout the 0.91 maintenance branch (which does not exist but > would be created as the maintenance branch). There was some > suggestion earlier that we leave Michael's work on a branch, but I > think we need to get it on the trunk so developers and svn users will > get it by default which will help us move more rapidly in shaking out > the remaining bugs and problems. > > Michael, since you know more about this than anyone, you should > probably spearhead the svn reorganization and let people know when the > changes become effective with some advance notice. I will update the > website with pointers to the relevant docs (your API_CHANGES and > Changelog and the relevant svn commands and anything else you think we > will need). > > If this seems like a reasonable plan, perhaps we should shoot for > doing this in a day or two. If any of you think this is the wrong > approach, let us know. > > JDH > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
