On Fri, Jun 3, 2011 at 4:39 AM, John Hunter <jdh2...@gmail.com> wrote: > On Thu, Jun 2, 2011 at 9:06 PM, Darren Dale <dsdal...@gmail.com> wrote: >> >> Before we made the git transition, I read about various workflows. >> What we are doing now is somewhat similar to what used to be done with >> svnmerge. I just googled "git workflow", and found >> http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html . >> See the section on "Merging Upwards": >> > > Responding to a few of the points mentioned above -- definitely +1 on more > releases. I have been the bottleneck here and can do more. With that in > mind, let's plan on getting a trunk release out with a 2 week timeline or > so.
That would be great. I am eager to merge the py3 stuff back into the main repository and start thinking about a 1.2 release. > I think there is a solid case for a release branch, so we can > test/refine/fix while allowing development in the trunk. Once it is > released, one suggestion is to can keep it around as maintenance but only > for release critical bugs so that if we discover a show stopper three weeks > after the release, we can cut a bugfix release w/ a shorted round of > testing. Perhaps if we limit it to release critical bugs, this will lower > the development burden on maintaining it and merging it. Sounds like a good idea. ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
