<div dir="ltr">It was my understanding (but I have not tested this personally) that several of the recipes in the cookbook could not yet be reproduced in 3.x. Is this true? If so, is the idea for 2.6 to be the last major version of 2.x and then all development to be shifted to 3.0, and part of this early 3.0 development would be on making sure that all of the functionality from 2.x work in 3.x? <div>
<br></div><div>I very much understand your statement of being in a perpetual state of never-yet-ready, but I think before we push more and more people to the 3.x branch, we need to make sure all the major pieces of functionality (mostly demonstrated through cookbook recipes) works in 3.x. This shiftover from 2.x to 3.x could, in fact, be the major facilitator of this, I just want to confirm the status of things. If that's the case, then I'm in favor of this.</div>
<div><br></div><div>Cameron</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 1, 2013 at 1:06 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 dir="ltr"><div>Matt,</div><div class="im"><div><br></div>On Tue, Oct 1, 2013 at 12:50 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:</div>
<div class="gmail_extra">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
* 2.6 be released on November 1, 2013, which gives several days after<br>
the "doc sprint." I will be working on docs leading up to the doc<br>
sprint. The code is in a good state at this point and we can release<br>
it at any time, but the documentation is the primary blocker for 2.6.<br>
* I have added three maintenance releases, every three months, for<br>
2.6.1, 2.6.2, 2.6.3 and 2.6.4. This is because will *not* be<br>
deprecating the 2.x series.<br></blockquote><div><br></div></div><div>How will this work inside the repo? Will be using branches and a single </div><div>repository? Will we accept pull requests into the 2.X codebase or only </div>
<div>accept PRs for 3.X and then backport as appropriate?</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
* 3.0 has been added with a tentative release on January 1, 2014. I<br>
have assessed the reliability of the code, and it seems to me that<br>
*even as it is*, it is considerably better than the 2.x line of<br>
development. The remaining struggles are all in documentation. A<br>
handful of operations are still outstanding -- clump finding and<br>
boolean objects most notably -- but the vast, vast majority are<br>
implemented.<br>
<br></blockquote><div><br></div></div><div>I also think it's important to address these two issues:</div><div><br></div><div><a href="https://bitbucket.org/yt_analysis/yt/issue/552/cut_region-doesnt-work-in-30" target="_blank">https://bitbucket.org/yt_analysis/yt/issue/552/cut_region-doesnt-work-in-30</a><br>
</div><div><a href="https://bitbucket.org/yt_analysis/yt/issue/499/missing-hierarchy-functions" target="_blank">https://bitbucket.org/yt_analysis/yt/issue/499/missing-hierarchy-functions</a><br></div><div class="im"><div>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I'd like to resolve this by proposing we wind down development on 2.X<br>
as best we can, and instead attempt to focus resources on 3.0. Until<br>
we do that, the biggest fish of the refactor/redesign simply can't<br>
land, which means we're in a self-perpetuating cycle of never getting<br>
to the point of being "ready."<br></blockquote><div><br></div></div><div>Agreed! I'm excited for everything to move over the 3.0 - it will be a relief </div><div>to make changes without having to worry about future merge conflicts.</div>
<div class="im">
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<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>
</blockquote></div></div><br></div></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">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>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Cameron Hummels<div>Postdoctoral Researcher</div><div>Steward Observatory</div><div>University of Arizona</div><div><a href="http://chummels.org" target="_blank">http://chummels.org</a></div>
</div>