<div dir="ltr">It looks like we're almost done: <a href="https://bitbucket.org/yt_analysis/yt/issues?milestone=2.5&milestone=&status=open&status=new&version=2.5">https://bitbucket.org/yt_analysis/yt/issues?milestone=2.5&milestone=&status=open&status=new&version=2.5</a><div>
<br></div><div style>Matt, please let us know if you'd like help with any of those issues.</div><div style><br></div><div style>I've been looking over the changelog and list of pull requests since the last release. Since last august, when we released 2.4, we've processed an astounding 195 pull requests, totaling 1056 changesets from 27 contributors. This isn't the largest release by number of lines or changsets, but it is by number of pull requests and number of contributors, reflecting yt's increasing role as a community-developed code. Some fun commands to play around with: </div>
<div style><br></div><div style>$ hg churn -r -c yt-2.3:yt-2.4</div><div style>$ hg churn -r -c yt-2.4:.</div><div style><br></div><div style>Well done everyone, I think this is a release that we can all be proud of.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 7, 2013 at 2:57 PM, Nathan Goldbaum <span dir="ltr"><<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>With all the activity today we're down to 10 open issues for the 2.5 release!</div>
<div><br></div><div><a href="https://bitbucket.org/yt_analysis/yt/issues?milestone=2.5&milestone=&status=open&status=new&version=2.5" target="_blank">https://bitbucket.org/yt_analysis/yt/issues?milestone=2.5&milestone=&status=open&status=new&version=2.5</a></div>
<div><div class="h5"><br><div><div>On Feb 7, 2013, at 12:25 PM, Matthew Turk wrote:</div><br><blockquote type="cite"><div>Hi all,<br><br>Okay, after a discussion in IRC about releasing 2.5, we've decided to<br>just start pushing ahead. I'd like to propose ([+-][01]) that we set<br>
a hard cutoff of a week from today, Valentine's day. If anything<br>doesn't make it in, that's fine. We just put out a release without it<br>and wrap it up in 2.6. (Yeah, we probably need a 2.6.)<br><br>The remaining blockers:<br>
<br> * I want Andrew's pull request to make it in. This is a huge win for<br>everyone. Once it's in, we can add documentation about it, and then<br>it'll be a big feature.<br> * John ZuHone has an outstanding piece of code that builds Enzo data<br>
from in-memory hierarchies. I would like to see this make it in, but<br>it is worth a release all by itself.<br> * The remaining tickets are mostly all documentation based. We need:<br>bootcamp in the docs, rotation information in the docs,<br>
offaxisprojection in the docs.<br> * We have a need for answer testing for Orion, FLASH, NYX and<br>optionally GDF datasets. I have been the bottleneck here. If you<br>have pinged me in the past, ping me again and I will do this with you.<br>
If we don't get to this by 14th, this will be bumped.<br><br>However: after 2.5 goes out, I would like for us to stop doing *major*<br>features on the 2.x branch and try to focus on 3.0. This may not be<br>possible for all things, but I would like to try to push for that. At<br>
a bare minimum, every new feature in 2.6 should be well-tested enough<br>that we can run those tests on 3.0 to determine if it is directly<br>portable. And future-compatible requirements will be in place for new<br>features in 2.6.<br>
<br>Also, I'd like to nominate John ZuHone to send out the release<br>announcement, particularly since he has worked so hard to put together<br>initial conditions generation in this release.<br><br>-Matt<br>_______________________________________________<br>
yt-dev mailing list<br><a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br><a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></blockquote></div><br></div></div></div></blockquote></div><br></div>