On Fri, Jun 3, 2011 at 10:04 AM, Benjamin Root <ben.r...@ou.edu> wrote:
> On Fri, Jun 3, 2011 at 3: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.
>>
>> 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.
>
> Why not just call it a release candidate and follow a similar process for it
> as numpy just did a short while ago?
>
> Plus, with regards to timing.  Do we want to release before or after the
> upcoming SciPy conference in July?  Depending on who will be there
> (unfortunately, I won't be), we might want to wait for after that conference
> to take advantage of any activity then.

If we have the resources, it might be better to release before, and
encourage activity at scipy to focus on py3 support (assuming it has
been merged into master by then).

------------------------------------------------------------------------------
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

Reply via email to