<div dir="ltr">I've been going over the docs and the cookbook and fixing as I can. Now that I'm back in Tucson, I can get on this again. That said, I am in agreement with Nathan that I think the docs need more eyes on them than just a couple of people. Notably, since I didn't do much on the move to 3.0, I don't know about all of the changes that need updating, but other developers who helped usher in 3.0 do.<div>
<br></div><div>Also, some of the functionality in the 3.0 cookbook appears to be broken. I'm correcting bugs as I can, but there are a lot of recipes that simply don't work because the functionality either never got updated to 3.0 or was somehow broken in the interim. I'm not promising to fix these larger issues, but by going through the recipes in the cookbook, we can at least identify the broken parts in yt. I'd say that I can be done with the recipes in the cookbook by this weekend, but then I imagine there will be more work to be done on some of this broken functionality before release. I guess we can comment further on this then.</div>
<div><br></div><div>I've also been going through and modifying pf and pf.h to ds in the docs, but one point of concern is that oftentimes pf and pf.h are used in the docstrings or in the internals of the code. A global search replace would fix this, but it may break some things along with it. I guess if we use the testing interface as a gauge for what gets broken, that might work, but if we're going to do a global replace, we should do it sooner as opposed to later to allow for all of the breakages to be discovered before release time.</div>
<div><br></div><div>I'd also add that perhaps we should have more tests in yt that cover some of the analysis modules, since that is a common place where breakage occurs.</div><div><br></div><div>I think end of June is a little bit ambitious. I'd say we work to get it done as soon as we can, but that we try to make sure all the requirements are met. I totally understand the desire to get 3.0 out and running asap, but I'm hesitant to release something with which we're effectively reintroducing ourselves to the community but which has bugs and/or incorrect docs.</div>
<div><br></div><div>Cameron</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 11, 2014 at 12:18 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Last I checked, the main blockers to 3.0 were:<br>
<br>
* Enabling answer testing (done)<br>
* Enabling doc building (done)<br>
* Redoing all relevant docs (in progress?)<br>
* Cookbook (in progress?)<br>
* Finishing up any outstanding frontend issues<br>
* Break the volume rendering interface, and rebuild it (sort of in progress)<br>
<br>
Does anybody know where we're at on these things? Looking over the board:<br>
<br>
<a href="https://trello.com/b/Y5XV4Hod/yt-3-0" target="_blank">https://trello.com/b/Y5XV4Hod/yt-3-0</a><br>
<br>
we're dangerously close. I think the final one, VR, might have to<br>
wait for 3.1, although I am very loathe to break API compat in a minor<br>
release. I think we might just have to.<br>
<br>
Cameron, Hilary and John ZuHone were all doing some doc stuff. How's<br>
that coming? How're you feeling about a release sometime before the<br>
end of June?<br>
<br>
Everybody else? Any other blockers, or things I forgot?<br>
<br>
-Matt<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>
</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>