John Hunter wrote: > On Nov 28, 2007 1:07 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: >> Great work everyone with getting the release out! >> >> Now is probably a good time to discuss how the SVN repository will look >> after the release. >> >> My thoughts are below -- any and all concerns or suggestions are >> welcome. I'm happy to do this work, and will probably wait until next >> week sometime to give the release some time to cool off, in case a major >> stopper bug is discovered in the meantime. A lot of this is perhaps >> obvious, but it doesn't hurt to be specific ;) >> >> PLAN: >> >> 1. Create a new branch based on the release version (I think Charlie >> last put it at r4477), in "branches/RELEASE_0_91_0". This branch will >> be "locked" to provide a little speedbump to remind us not to commit to >> it. This branch is useful to have as a point of comparison -- though >> not strictly necessary, since we know the release version on the trunk. > > Bearing in mind that I am a branch newbie, this seems a bit overly > complicated. I envisioned having a single branch which would be the > svn trunk before you merge your transforms in. Call this MAINTAIN_91 > or something like that. Then merge the transforms branch into the > trunk, and close or move the transforms branch as you see fit. > > That way we have one active branch (the 0.91 maintenance) and one > trunk. I don't see the benefit of having RELEASE_0_91_0 and MAINT_0_x > branches, since we can use use -r checkouts to get 0.91.0 right? > Basically, I hope we can get by w/o multiple branches for the 91 > maintenance. But feel free to educate me :-)
You're correct -- it isn't strictly necessary. IMHO, however, it makes the released 0.91 version more obvious. As it stands now, one has to know to look for the revision associated with 0.91 in the CHANGELOG. It's an attempt to follow standard SVN practice to make things easier for someone coming into the project. Which leads me to a "Doh!" -- it should be under "tags", rather than under "branches". (Of course, in SVN there's no difference, other than the name...) I also should revise these names to fit in with the mpl's tags brought over from CVS: branches/RELEASE_0_91_0 ---> tags/v0_91_0 branches/MAINT_0_x ---> branches/v0_91_maint Cheers, Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
