Cameron, I completely agree -- we should do more of that!
I think that, since I am going off the grid very soon, I will not be
able to finish up everything that needs to go in to 3.0a3. There are
a couple outstanding pull requests from me, Doug, and others that need
to go in before it can be rolled out, and I also need to write up the
documentation. I think it will need to be delayed until mid-August.
Fortunately, I don't think this is such a big deal, since the code in
yt-3.0 is in a usable state, but I am sorry to have missed the
On Wed, Jul 17, 2013 at 10:13 AM, Cameron Hummels <chummels(a)gmail.com> wrote:
Thanks for the update to all of this on this. I am very pleased to hear
that there will be notebooks demonstrating some of the new features in the
release. I would be in favor of having this be standard practice in
releases, despite the additional time required to do notebooks. I don't
know about anyone else, but from now on, when I write significant additional
functionality into the code base, I'd be happy to include a notebook
demonstrating how to use it. Thanks for doing this!
On Mon, Jul 15, 2013 at 9:13 AM, Matthew Turk <matthewturk(a)gmail.com> wrote:
I'm starting the release process of yt 3.0a3 today, but I won't finish
it for a few days. Basically, I'm writing up a bunch of notebooks
demoing new features and showing speed/memory improvements. So the
release will likely be delayed until later this week.
Any outstanding pull requests you'd like to have go in should be
issued today or tomorrow morning, and I'll try to review and have them
go in. If there are major outstanding bugs, or improvements that
aren't ready to land yet, we can hold off a few more days but
absolutely no later than Thursday of next week.
PS As a sidenote, I will be out of email contact for some time
not-yet-determined starting between July 30 and through at least
yt-dev mailing list
University of Arizona
yt-dev mailing list