Hi all, Last I checked, the main blockers to 3.0 were: * Enabling answer testing (done) * Enabling doc building (done) * Redoing all relevant docs (in progress?) * Cookbook (in progress?) * Finishing up any outstanding frontend issues * Break the volume rendering interface, and rebuild it (sort of in progress) Does anybody know where we're at on these things? Looking over the board: https://trello.com/b/Y5XV4Hod/yt-3-0 we're dangerously close. I think the final one, VR, might have to wait for 3.1, although I am very loathe to break API compat in a minor release. I think we might just have to. Cameron, Hilary and John ZuHone were all doing some doc stuff. How's that coming? How're you feeling about a release sometime before the end of June? Everybody else? Any other blockers, or things I forgot? -Matt
On Wed, Jun 11, 2014 at 12:18 PM, Matthew Turk
Hi all,
Last I checked, the main blockers to 3.0 were:
* Enabling answer testing (done) * Enabling doc building (done) * Redoing all relevant docs (in progress?) * Cookbook (in progress?) * Finishing up any outstanding frontend issues * Break the volume rendering interface, and rebuild it (sort of in progress)
Does anybody know where we're at on these things? Looking over the board:
https://trello.com/b/Y5XV4Hod/yt-3-0
we're dangerously close. I think the final one, VR, might have to wait for 3.1, although I am very loathe to break API compat in a minor release. I think we might just have to.
Cameron, Hilary and John ZuHone were all doing some doc stuff. How's that coming? How're you feeling about a release sometime before the end of June?
Everybody else? Any other blockers, or things I forgot?
I'm in the middle of going over the plotting docs. I think the docs need many eyes to go over them. I also think we need to decide on whether or not it's worth standardizing the terminology we use across the docs. That means things like ds vs pf, import yt vs from yt.mods import *. I know I haven't brought this up, but one internal thing I'd like to at least bring up is renaming all the internal references to "pf" objects to be "ds". I think this just means a global search and replace. One downside is that it might break user scripts if people are using the internal API. I worry about releasing 3.0 with internally inconsistent naming throughout the codebase.
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I have some more docs to write, but not many.
It's not super-crucial, but I would like to get 100% unit and answer tests passing on Windows before release. At the moment, only a few unit tests are failing. If others feel like this is not important enough to be a blocker, I am fine with that.
I would say early July, maybe.
On Jun 11, 2014, at 3:18 PM, Matthew Turk
Hi all,
Last I checked, the main blockers to 3.0 were:
* Enabling answer testing (done) * Enabling doc building (done) * Redoing all relevant docs (in progress?) * Cookbook (in progress?) * Finishing up any outstanding frontend issues * Break the volume rendering interface, and rebuild it (sort of in progress)
Does anybody know where we're at on these things? Looking over the board:
https://trello.com/b/Y5XV4Hod/yt-3-0
we're dangerously close. I think the final one, VR, might have to wait for 3.1, although I am very loathe to break API compat in a minor release. I think we might just have to.
Cameron, Hilary and John ZuHone were all doing some doc stuff. How's that coming? How're you feeling about a release sometime before the end of June?
Everybody else? Any other blockers, or things I forgot?
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
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.
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.
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.
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.
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.
Cameron
On Wed, Jun 11, 2014 at 12:18 PM, Matthew Turk
Hi all,
Last I checked, the main blockers to 3.0 were:
* Enabling answer testing (done) * Enabling doc building (done) * Redoing all relevant docs (in progress?) * Cookbook (in progress?) * Finishing up any outstanding frontend issues * Break the volume rendering interface, and rebuild it (sort of in progress)
Does anybody know where we're at on these things? Looking over the board:
https://trello.com/b/Y5XV4Hod/yt-3-0
we're dangerously close. I think the final one, VR, might have to wait for 3.1, although I am very loathe to break API compat in a minor release. I think we might just have to.
Cameron, Hilary and John ZuHone were all doing some doc stuff. How's that coming? How're you feeling about a release sometime before the end of June?
Everybody else? Any other blockers, or things I forgot?
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
Thanks for the replies, everyone. If you could try to keep the
blockers updated in Trello, it'll really help development. I agree,
we need as many eyes as possible on the docs before it goes out.
The main things that are on my agenda, which are driving things:
* We may be getting a reasonable amount of exposure in mid-June (more
on that if/when it happens)
* SciPy is an ideal time to have a release just out
* At the end of July I'm going on vacation for a couple weeks with
limited email access
So before that stuff starts kicking in, I would really liek to get an
idea of what things need to be accomplished. That way, I and others
can continue working on them trying to check them off the list. I'd
really like to avoid polishing until perfection, and instead focus on
a shippable release.
Thanks,
Matt
On Wed, Jun 11, 2014 at 2:18 PM, Matthew Turk
Hi all,
Last I checked, the main blockers to 3.0 were:
* Enabling answer testing (done) * Enabling doc building (done) * Redoing all relevant docs (in progress?) * Cookbook (in progress?) * Finishing up any outstanding frontend issues * Break the volume rendering interface, and rebuild it (sort of in progress)
Does anybody know where we're at on these things? Looking over the board:
https://trello.com/b/Y5XV4Hod/yt-3-0
we're dangerously close. I think the final one, VR, might have to wait for 3.1, although I am very loathe to break API compat in a minor release. I think we might just have to.
Cameron, Hilary and John ZuHone were all doing some doc stuff. How's that coming? How're you feeling about a release sometime before the end of June?
Everybody else? Any other blockers, or things I forgot?
-Matt
participants (4)
-
Cameron Hummels -
John ZuHone -
Matthew Turk -
Nathan Goldbaum