[yt-dev] Feature freeze for 3.3

[Nathan Goldbaum]

Feature freeze starting next Wednesday sounds fine to me.

It might also help to have a slack sprint to fix issues sometime in the
next couple weeks. That was pretty successful the last time we did it.

On Thu, Jun 2, 2016 at 10:18 AM, Matthew Turk <matthewturk at gmail.com> wrote:

> Hi folks,
>
> Here are the outstanding issues for releasing 3.3:
>
>
> https://bitbucket.org/yt_analysis/yt/issues?status=new&status=open&version=3.3
>
> I'd like to propose, and hold myself accountable to, a feature freeze
> for 3.3.  I think we should give a pass on *already* open pull
> requests, but set up a freeze starting Wednesday for non-bugfix
> changes until 3.3 is released, after which the gates can re-open.  If
> anyone has any strong objections, let's bump it, but I'd like to see
> the release go out and not creep too far.  (It's already got quite a
> lot in it!)
>
> I'm going to start picking out bugs today to get going.  Thanks to
> Nathan and Cameron for identifying these bugs for the 3.3 release,
> which was a non-trivial task.
>
> -Matt
> _______________________________________________
> 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/20160602/46c1ecd7/attachment.htm>