[yt-dev] Stable release

[Nathan Goldbaum]

On Mon, Jul 6, 2015 at 4:04 AM, Britton Smith <brittonsmith at gmail.com>
wrote:

> Hi Nathan,
>
> This was discussed somewhat at last week's yt team meeting.  It was
> decided that we would try to get back to doing the regular releases and
> that in between releases Matt would be responsible for keeping stable and
> dev synced on bug fixes.  Matt, please speak up if I am in error on this.
>
> As for what to do right now, I think it's a good idea to backport the bug
> fixes to stable and do a minor release.  I think we definitely need this.
> However, rather than having one person take this on by themselves, I
> propose this be done in hangout with a few people present to share the
> burden.  If anyone is up for doing this in the near future (say, this
> week), please respond.  Or maybe this could be a job for the first PR
> review hangout?  What do we think about that?
>

Sure, let's do it this week.


>
> Finally, as you might have noticed, I have become a big fan of the idea of
> taking care of business in group settings via hangouts.  I think it would
> be a good idea to try and decrease the large efforts made by a single
> person and the text-only communication and increase the face-to-face
> communication and working in groups.  Just my two cents, that I realize
> I've been quite vocal on in the past hour.
>
> Britton
>
> On Tue, Jun 30, 2015 at 3:57 AM, Nathan Goldbaum <nathan12343 at gmail.com>
> wrote:
>
>>  Hi all,
>>
>> A while back we were intending to backport bugfixes from the yt branch to
>> the stable branch and then regularly issue bugfix releases. This hasn't
>> happened, and new users in particular feel the pain this causes.
>>
>> Does someone want to volunteer to backport bugfix pull requests to the
>> stable branch? It should be more or less automatic, although you will
>> likely need to do it one pull request at a time, and it will be hard to
>> review. This would be a great, relatively straightforward if tedious task
>> to do at the scipy sprints, if anyone is going to that.
>>
>> Should we just abandon this idea and go ahead and release 3.2 sooner
>> rather than later?
>>
>> Is there a way to sustainably make sure bugfixes eventually make their
>> way to the stable branch, either with or without changing our development
>> workflow?
>>
>> -Nathan
>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20150706/2bf500b4/attachment.html>