John Hunter wrote: > On Sat, May 31, 2008 at 9:19 AM, Darren Dale <[EMAIL PROTECTED]> wrote: > >> I'll be working on converting docstrings to rest this weekend. Should any of >> this be done on the branch? Or should we just focus on the trunk? >> > > As far as I am concerned, the documentation effort is for the trunk. > The only reason to do them on the branch too is to make merges of > other code changes easier, which may be a compelling reason. If the > docstrings get far out of whack, it may make merging other changes > very painful. But at the same time, I don't want the burden of > trying to keep the two in sync stopping you from getting the work done > that you need to do. Maybe you can try it and see how hard it is, and > if proves to be too much of an impediment, just concentrate on the > trunk. Michael, any advice here? > I was away on the weekend, so just getting back. Darren: you rock. The documentation is looking great!
I agree with John -- I think the documentation effort should be focused on the trunk. Now that we have (apparently) such a stable 0.91.3, hopefully the maintenance branch will be much less frequently modified anyway. Theoretically, we should only run into merge conflicts related to docstrings if the docstrings on the maintenance branch are themselves edited. If we're just going to be doing bugfixes on the branch, that seems unlikely. Cheers, Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
