proposing a yt-3.2 release
Hi everyone, Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible. Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this. I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable. For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps. Britton
does this include the new VR interface? I'm +1 if it is the old interface for 3.2. On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment. On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:
does this include the new VR interface? I'm +1 if it is the old interface for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1 On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com> wrote:
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
does this include the new VR interface? I'm +1 if it is the old interface for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
We do have one blocker, at least from my point of view. At the moment I am -1. 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. 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. Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out). Best, John
On Jul 9, 2015, at 2:08 PM, Matthew Turk <matthewturk@gmail.com> wrote:
+1
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com> wrote:
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
does this include the new VR interface? I'm +1 if it is the old interface for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Thu, Jul 9, 2015 at 11:12 AM, John ZuHone <jzuhone@gmail.com> wrote:
We do have one blocker, at least from my point of view. At the moment I am -1.
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.
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.
Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out).
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. 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). 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. -Nathan
Best,
John
On Jul 9, 2015, at 2:08 PM, Matthew Turk <matthewturk@gmail.com> wrote:
+1
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with
docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
does this include the new VR interface? I'm +1 if it is the old
interface
for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs
from
the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in
docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do
someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com> wrote: the the this, then proposal.
If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I’m happy to devote effort for the rest of this week and next to finish the Python 3 stuff up. Kacper, where do we stand on Python 3 testing?
On Jul 9, 2015, at 2:16 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
On Thu, Jul 9, 2015 at 11:12 AM, John ZuHone <jzuhone@gmail.com <mailto:jzuhone@gmail.com>> wrote: We do have one blocker, at least from my point of view. At the moment I am -1.
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.
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.
Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out).
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.
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).
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.
-Nathan
Best,
John
On Jul 9, 2015, at 2:08 PM, Matthew Turk <matthewturk@gmail.com <mailto:matthewturk@gmail.com>> wrote:
+1
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com <mailto:brittonsmith@gmail.com>> wrote:
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu <mailto:michael.zingale@stonybrook.edu>> wrote:
does this include the new VR interface? I'm +1 if it is the old interface for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com <mailto:brittonsmith@gmail.com>> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 <tel:631-632-8225> e-mail: Michael.Zingale@stonybrook.edu <mailto:Michael.Zingale@stonybrook.edu> web: http://www.astro.sunysb.edu/mzingale <http://www.astro.sunysb.edu/mzingale> github: http://github.com/zingale <http://github.com/zingale>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I am also +1 on the proposed plan. On Thu, Jul 9, 2015 at 11:08 AM, Matthew Turk <matthewturk@gmail.com> wrote:
+1
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
does this include the new VR interface? I'm +1 if it is the old
interface
for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs
from
the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in
docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do
someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com> wrote: the this, then proposal.
If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ 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
On 07/09/2015 01:30 PM, John ZuHone wrote:
I’m happy to devote effort for the rest of this week and next to finish the Python 3 stuff up.
Kacper, where do we stand on Python 3 testing?
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!). Cheers, Kacper
On Jul 9, 2015, at 2:16 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
On Thu, Jul 9, 2015 at 11:12 AM, John ZuHone <jzuhone@gmail.com <mailto:jzuhone@gmail.com>> wrote: We do have one blocker, at least from my point of view. At the moment I am -1.
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.
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.
Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out).
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.
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).
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.
-Nathan
Best,
John
On Jul 9, 2015, at 2:08 PM, Matthew Turk <matthewturk@gmail.com <mailto:matthewturk@gmail.com>> wrote:
+1
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com <mailto:brittonsmith@gmail.com>> wrote:
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu <mailto:michael.zingale@stonybrook.edu>> wrote:
does this include the new VR interface? I'm +1 if it is the old interface for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com <mailto:brittonsmith@gmail.com>> wrote:
Hi everyone,
Nathan and I just met briefly to discuss backporting all bugfix PRs from the development branch to stable so as to do a minor release. This has become absolutely necessary as a large number of bugs have appeared and been fixed since the last release, which was nearly 6 months ago. By my rough estimate, there have been about 200 PRs accepted since the last release, with a large fraction of them being bug fixes. Therefore, it seemed to both Nathan and I that there were simply too many changesets that need to be picked out of dev and transplanted to stable for such an operation to be feasible.
Instead, a far simpler solution is to bite the bullet and do a 3.2 release with everything currently in dev. Fortunately, as we require passing tests and documentation of new features, this would require relatively little effort. Most of the work is cleaning up errors in the docs build, for which Nathan is filing tickets as I write this.
I want to be clear that we desperately need a new release with the number of bugs that have been fixed since the last one. If we do not do this, then someone else needs to step up and backport all those bugfixes to stable.
For now, can I please get a +-1 on whether you agree with this proposal. If this meets with approval, then I will coordinate taking the next steps.
Britton
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 <tel:631-632-8225> e-mail: Michael.Zingale@stonybrook.edu <mailto:Michael.Zingale@stonybrook.edu> web: http://www.astro.sunysb.edu/mzingale <http://www.astro.sunysb.edu/mzingale> github: http://github.com/zingale <http://github.com/zingale>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org <http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
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. Britton On Thu, Jul 9, 2015 at 8:21 PM, Kacper Kowalik <xarthisius.kk@gmail.com> wrote:
On 07/09/2015 01:30 PM, John ZuHone wrote:
I’m happy to devote effort for the rest of this week and next to finish the Python 3 stuff up.
Kacper, where do we stand on Python 3 testing?
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!).
Cheers, Kacper
On Jul 9, 2015, at 2:16 PM, Nathan Goldbaum <nathan12343@gmail.com>
wrote:
On Thu, Jul 9, 2015 at 11:12 AM, John ZuHone <jzuhone@gmail.com <mailto: jzuhone@gmail.com>> wrote: We do have one blocker, at least from my point of view. At the moment I am -1.
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.
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.
Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out).
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.
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).
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.
-Nathan
Best,
John
On Jul 9, 2015, at 2:08 PM, Matthew Turk <matthewturk@gmail.com
<mailto:matthewturk@gmail.com>> wrote:
+1
On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <brittonsmith@gmail.com <mailto:brittonsmith@gmail.com>> wrote:
This does not explicitly include the VR refactor, unless it happened to be approved in the very near future. Assuming the remaining issues with the docs build were dealt with, it would be exactly what's in dev at this moment.
On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale <michael.zingale@stonybrook.edu <mailto:michael.zingale@stonybrook.edu>> wrote:
does this include the new VR interface? I'm +1 if it is the old interface for 3.2.
On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <brittonsmith@gmail.com <mailto:brittonsmith@gmail.com>> wrote:
> > Hi everyone, > > Nathan and I just met briefly to discuss backporting all bugfix PRs > from > the development branch to stable so as to do a minor release. This > has > become absolutely necessary as a large number of bugs have appeared > and been > fixed since the last release, which was nearly 6 months ago. By my > rough > estimate, there have been about 200 PRs accepted since the last > release, > with a large fraction of them being bug fixes. Therefore, it seemed > to both > Nathan and I that there were simply too many changesets that need to > be > picked out of dev and transplanted to stable for such an operation > to be > feasible. > > Instead, a far simpler solution is to bite the bullet and do a 3.2 > release with everything currently in dev. Fortunately, as we require > passing tests and documentation of new features, this would require > relatively little effort. Most of the work is cleaning up errors in > the > docs build, for which Nathan is filing tickets as I write this. > > I want to be clear that we desperately need a new release with the > number > of bugs that have been fixed since the last one. If we do not do > this, then > someone else needs to step up and backport all those bugfixes to > stable. > > For now, can I please get a +-1 on whether you agree with this > proposal. > If this meets with approval, then I will coordinate taking the next > steps. > > Britton > > _______________________________________________ > yt-dev mailing list > yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org < > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org> > >
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 <tel:631-632-8225> e-mail: Michael.Zingale@stonybrook.edu <mailto: Michael.Zingale@stonybrook.edu> web: http://www.astro.sunysb.edu/mzingale < http://www.astro.sunysb.edu/mzingale> github: http://github.com/zingale <http://github.com/zingale>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org < http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org < http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org < http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org <mailto:yt-dev@lists.spacepope.org> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org < http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (7)
-
Britton Smith -
Cameron Hummels -
John ZuHone -
Kacper Kowalik -
Matthew Turk -
Michael Zingale -
Nathan Goldbaum