<div dir="ltr">I think it's important we not fall into the trap of continually delaying a release until a feature is ready, especially when there is a genuine need for a release to happen. There will always be another release. I think we should put a hard deadline on releasing 3.2, even if that means that 3.3 comes out two weeks later. I propose that we release 3.2 next Friday by hook or by crook.<div><br></div><div>Britton</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 9, 2015 at 8:21 PM, Kacper Kowalik <span dir="ltr"><<a href="mailto:xarthisius.kk@gmail.com" target="_blank">xarthisius.kk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 07/09/2015 01:30 PM, John ZuHone wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I’m happy to devote effort for the rest of this week and next to finish the Python 3 stuff up.<br>
<br>
Kacper, where do we stand on Python 3 testing?<br>
</blockquote>
<br></span>
Unit tests are run for every PR but results are not being reported by yt-fido. They currently failing (FAILED (errors=8)). Answer tests had some weird issues. I vaguely remember it was related to names that were stored in answers (string not working with py3 surprise, surprise!).<br>
<br>
Cheers,<br>
Kacper<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Jul 9, 2015, at 2:16 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>> wrote:<br>
<br>
<br>
<br></span><span class="">
On Thu, Jul 9, 2015 at 11:12 AM, John ZuHone <<a href="mailto:jzuhone@gmail.com" target="_blank">jzuhone@gmail.com</a> <mailto:<a href="mailto:jzuhone@gmail.com" target="_blank">jzuhone@gmail.com</a>>> wrote:<br>
We do have one blocker, at least from my point of view. At the moment I am -1.<br>
<br>
We have done a lot of work to get a single yt codebase for Python 2 and 3, but we have not (to my knowledge) had a single test run where all tests are passing under Python 3, including answer tests.<br>
<br>
Since the Python 3 stuff is everywhere in the code, we need to verify that all the tests pass (I bet they won’t just yet) before we release.<br>
<br>
Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out).<br>
<br>
I brought this up while talking to Britton earlier. I agree that ideally the python3 stuff would need to be shored up for 3.2, including full testing.<br>
<br>
That said, one way to get around this is to say 3.2 has preliminary beta-level support for python3, but that will support will come in 3.3 (or even in a 3.2.1 release).<br>
<br>
If we can quickly-ish get full python3 support then great, I just don't want to be blocked on developer time for a while.<br>
<br>
-Nathan<br>
<br>
<br>
Best,<br>
<br>
John<br>
<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Jul 9, 2015, at 2:08 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a> <mailto:<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>>> wrote:<br>
<br>
+1<br>
<br></span><span class="">
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a> <mailto:<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>>> wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
This does not explicitly include the VR refactor, unless it happened to be<br>
approved in the very near future. Assuming the remaining issues with the<br>
docs build were dealt with, it would be exactly what's in dev at this<br>
moment.<br>
<br>
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale<br></span>
<<a href="mailto:michael.zingale@stonybrook.edu" target="_blank">michael.zingale@stonybrook.edu</a> <mailto:<a href="mailto:michael.zingale@stonybrook.edu" target="_blank">michael.zingale@stonybrook.edu</a>>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
does this include the new VR interface? I'm +1 if it is the old interface<br>
for 3.2.<br>
<br></span>
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a> <mailto:<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
Hi everyone,<br>
<br>
Nathan and I just met briefly to discuss backporting all bugfix PRs from<br>
the development branch to stable so as to do a minor release. This has<br>
become absolutely necessary as a large number of bugs have appeared and been<br>
fixed since the last release, which was nearly 6 months ago. By my rough<br>
estimate, there have been about 200 PRs accepted since the last release,<br>
with a large fraction of them being bug fixes. Therefore, it seemed to both<br>
Nathan and I that there were simply too many changesets that need to be<br>
picked out of dev and transplanted to stable for such an operation to be<br>
feasible.<br>
<br>
Instead, a far simpler solution is to bite the bullet and do a 3.2<br>
release with everything currently in dev. Fortunately, as we require<br>
passing tests and documentation of new features, this would require<br>
relatively little effort. Most of the work is cleaning up errors in the<br>
docs build, for which Nathan is filing tickets as I write this.<br>
<br>
I want to be clear that we desperately need a new release with the number<br>
of bugs that have been fixed since the last one. If we do not do this, then<br>
someone else needs to step up and backport all those bugfixes to stable.<br>
<br>
For now, can I please get a +-1 on whether you agree with this proposal.<br>
If this meets with approval, then I will coordinate taking the next steps.<br>
<br>
Britton<br>
<br>
_______________________________________________<br>
yt-dev mailing list<br>
</span><a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a> <mailto:<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a> <<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a>><br>
<br>
</blockquote><span class="">
<br>
<br>
<br>
--<br>
Michael Zingale<br>
Associate Professor<br>
<br>
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY<br>
11794-3800<br></span>
phone: <a href="tel:631-632-8225" value="+16316328225" target="_blank">631-632-8225</a> <tel:<a href="tel:631-632-8225" value="+16316328225" target="_blank">631-632-8225</a>><br>
e-mail: <a href="mailto:Michael.Zingale@stonybrook.edu" target="_blank">Michael.Zingale@stonybrook.edu</a> <mailto:<a href="mailto:Michael.Zingale@stonybrook.edu" target="_blank">Michael.Zingale@stonybrook.edu</a>><br>
web: <a href="http://www.astro.sunysb.edu/mzingale" rel="noreferrer" target="_blank">http://www.astro.sunysb.edu/mzingale</a> <<a href="http://www.astro.sunysb.edu/mzingale" rel="noreferrer" target="_blank">http://www.astro.sunysb.edu/mzingale</a>><br>
github: <a href="http://github.com/zingale" rel="noreferrer" target="_blank">http://github.com/zingale</a> <<a href="http://github.com/zingale" rel="noreferrer" target="_blank">http://github.com/zingale</a>><br>
<br>
<br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a> <mailto:<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a> <<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a>><br>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a> <mailto:<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a> <<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a>><br>
<br>
</blockquote>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a> <mailto:<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a> <<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a>><br>
</blockquote>
<br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a> <mailto:<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a> <<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a>><span class=""><br>
<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</span></blockquote><span class="">
<br>
<br>
<br>
<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<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" rel="noreferrer" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div>