Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. So how about we start a 4.0.2 milestone to keep track of our progress with backports ? This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io As far as I understand, this bot can create backport PRs mirroring patches associated with a milestone, itself attached to dedicated release branch. Let me know if you have any thoughts on that too. Cheers, Clément
Hi,
I think a) we should do a point release and b) Yes, that tool looks
quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. So how about we start a 4.0.2 milestone to keep track of our progress with backports ?
This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io As far as I understand, this bot can create backport PRs mirroring patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the yt
So how about we start a 4.0.2 milestone to keep track of our progress with backports ?
This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io As far as I understand, this bot can create backport PRs mirroring
4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com
-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
This doesn’t seem to be controversial so I’m going to go ahead and start a 4.0.2 milestone. I’ll try to use the following tool to create back port PRs: https://github.com/sqren/backport Cheers
On 7 Oct 2021, at 19:45, Cameron Hummels
wrote: Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
wrote: Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. So how about we start a 4.0.2 milestone to keep track of our progress with backports ?
This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: [https://meeseeksbox.github.io](https://meeseeksbox.github.io/) As far as I understand, this bot can create backport PRs mirroring patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com
--
Cameron Hummels Computational Astrophysicist California Institute of Technology
Hi Clement, could you hold off just a bit? I think I'd like to get
some more clarity through issue 3553 first.
On Tue, Oct 12, 2021 at 9:08 AM Clément Robert via yt-dev
This doesn’t seem to be controversial so I’m going to go ahead and start a 4.0.2 milestone. I’ll try to use the following tool to create back port PRs: https://github.com/sqren/backport Cheers
On 7 Oct 2021, at 19:45, Cameron Hummels
wrote: Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
wrote: Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. So how about we start a 4.0.2 milestone to keep track of our progress with backports ?
This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io As far as I understand, this bot can create backport PRs mirroring patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com
-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
should I do a docs PR saying that for BoxLib / AMReX codes you need to
yt.load doesn't work and show how to manually load things? This affects a
dozen or so codes.
On Tue, Oct 12, 2021 at 10:09 AM Matthew Turk
Hi Clement, could you hold off just a bit? I think I'd like to get some more clarity through issue 3553 first.
On Tue, Oct 12, 2021 at 9:08 AM Clément Robert via yt-dev
wrote: This doesn’t seem to be controversial so I’m going to go ahead and start
Cheers
On 7 Oct 2021, at 19:45, Cameron Hummels
wrote: Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
wrote: Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the
yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon.
So how about we start a 4.0.2 milestone to keep track of our progress with backports ?
This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io As far as I understand, this bot can create backport PRs mirroring
a 4.0.2 milestone. I’ll try to use the following tool to create back port PRs: https://github.com/sqren/backport patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com
-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: michael.zingale@stonybrook.edu
-- Michael Zingale Professor of Physics and Astronomy Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: michael.zingale@stonybrook.edu *web*: https://zingale.github.io github: https://github.com/zingale http://github.com/zingale
Hi Mike, I actually don't have much context on this. Can you point to
a bug report or PR or something?
On Tue, Oct 12, 2021 at 9:12 AM Michael Zingale
should I do a docs PR saying that for BoxLib / AMReX codes you need to yt.load doesn't work and show how to manually load things? This affects a dozen or so codes.
On Tue, Oct 12, 2021 at 10:09 AM Matthew Turk
wrote: Hi Clement, could you hold off just a bit? I think I'd like to get some more clarity through issue 3553 first.
On Tue, Oct 12, 2021 at 9:08 AM Clément Robert via yt-dev
wrote: This doesn’t seem to be controversial so I’m going to go ahead and start a 4.0.2 milestone. I’ll try to use the following tool to create back port PRs: https://github.com/sqren/backport Cheers
On 7 Oct 2021, at 19:45, Cameron Hummels
wrote: Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
wrote: Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. So how about we start a 4.0.2 milestone to keep track of our progress with backports ?
This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io As far as I understand, this bot can create backport PRs mirroring patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com
-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: michael.zingale@stonybrook.edu
-- Michael Zingale Professor of Physics and Astronomy
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: michael.zingale@stonybrook.edu web: https://zingale.github.io github: https://github.com/zingale
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
issue is here:
https://github.com/yt-project/yt/issues/3005
the workaround is to do:
from yt.frontends.boxlib.api import CastroDataset
ds = CastroDataset(
Hi Mike, I actually don't have much context on this. Can you point to a bug report or PR or something?
On Tue, Oct 12, 2021 at 9:12 AM Michael Zingale
wrote: should I do a docs PR saying that for BoxLib / AMReX codes you need to
yt.load doesn't work and show how to manually load things? This affects a dozen or so codes.
On Tue, Oct 12, 2021 at 10:09 AM Matthew Turk
Hi Clement, could you hold off just a bit? I think I'd like to get some more clarity through issue 3553 first.
On Tue, Oct 12, 2021 at 9:08 AM Clément Robert via yt-dev
wrote: This doesn’t seem to be controversial so I’m going to go ahead and
start a 4.0.2 milestone. I’ll try to use the following tool to create back
Cheers
On 7 Oct 2021, at 19:45, Cameron Hummels
wrote: Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
wrote: Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects
strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: Hi yt-dev ! I hope you’re all doing well. I would like to propose we plan for another bug fix release for
So how about we start a 4.0.2 milestone to keep track of our
This time around, they’ll have to be manually performed, which I
believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io
As far as I understand, this bot can create backport PRs mirroring
wrote: port PRs: https://github.com/sqren/backport the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. progress with backports ? patches associated with a milestone, itself attached to dedicated release branch.
Let me know if you have any thoughts on that too. Cheers, Clément
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com
-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: michael.zingale@stonybrook.edu
-- Michael Zingale Professor of Physics and Astronomy
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: michael.zingale@stonybrook.edu web: https://zingale.github.io github: https://github.com/zingale
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: michael.zingale@stonybrook.edu
-- Michael Zingale Professor of Physics and Astronomy Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: michael.zingale@stonybrook.edu *web*: https://zingale.github.io github: https://github.com/zingale http://github.com/zingale
Thank you, Mike -- I missed this. I'll engage on the issue.
On Tue, Oct 12, 2021 at 9:38 AM Michael Zingale
issue is here:
https://github.com/yt-project/yt/issues/3005
the workaround is to do:
from yt.frontends.boxlib.api import CastroDataset ds = CastroDataset(
) so we should advertise that in the docs. I know that is needed for Castro, Maestro, Nyx, and probably WarpX. I don't know about the other AMReX codes.
On Tue, Oct 12, 2021 at 10:35 AM Matthew Turk
wrote: Hi Mike, I actually don't have much context on this. Can you point to a bug report or PR or something?
On Tue, Oct 12, 2021 at 9:12 AM Michael Zingale
wrote: should I do a docs PR saying that for BoxLib / AMReX codes you need to yt.load doesn't work and show how to manually load things? This affects a dozen or so codes.
On Tue, Oct 12, 2021 at 10:09 AM Matthew Turk
wrote: Hi Clement, could you hold off just a bit? I think I'd like to get some more clarity through issue 3553 first.
On Tue, Oct 12, 2021 at 9:08 AM Clément Robert via yt-dev
wrote: This doesn’t seem to be controversial so I’m going to go ahead and start a 4.0.2 milestone. I’ll try to use the following tool to create back port PRs: https://github.com/sqren/backport Cheers
On 7 Oct 2021, at 19:45, Cameron Hummels
wrote: Sounds good to me. Thanks for proposing this, Clément.
On Thu, Oct 7, 2021 at 10:35 AM Matthew Turk
wrote: Hi,
I think a) we should do a point release and b) Yes, that tool looks quite nice. I think we should try it unless someone objects strongly!
On Thu, Oct 7, 2021 at 10:55 AM Clément Robert via yt-dev
wrote: > > Hi yt-dev ! > I hope you’re all doing well. > I would like to propose we plan for another bug fix release for the yt 4.0.x series. We had approximately 20 merged bug fixes since yt 4.0.1 (excluding docs and infrastructure fixes), and a couple bug fixing PRs that could realistically go in soon. > So how about we start a 4.0.2 milestone to keep track of our progress with backports ? > > This time around, they’ll have to be manually performed, which I believe is one reason why we don’t do this more often, but in the future, we could automate the back porting process. For instance, Matplotlib and Ipython are using this tool: https://meeseeksbox.github.io > As far as I understand, this bot can create backport PRs mirroring patches associated with a milestone, itself attached to dedicated release branch. > > Let me know if you have any thoughts on that too. > Cheers, > Clément > > > _______________________________________________ > yt-dev mailing list -- yt-dev@python.org > To unsubscribe send an email to yt-dev-leave@python.org > https://mail.python.org/mailman3/lists/yt-dev.python.org/ > Member address: matthewturk@gmail.com _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: chummels@gmail.com -- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: michael.zingale@stonybrook.edu
-- Michael Zingale Professor of Physics and Astronomy
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: michael.zingale@stonybrook.edu web: https://zingale.github.io github: https://github.com/zingale
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: michael.zingale@stonybrook.edu
-- Michael Zingale Professor of Physics and Astronomy
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: michael.zingale@stonybrook.edu web: https://zingale.github.io github: https://github.com/zingale
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address: matthewturk@gmail.com
participants (4)
-
Cameron Hummels
-
Clément Robert
-
Matthew Turk
-
Michael Zingale