Proposal for a roadmap to yt 4.1
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then. I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0 I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable. There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely 1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890 To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label. You can help by discussing and triaging open issues and PRs to and from the milestone. It’s also a good time to get feature PRs to the finish line. We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future. Any feedback is most welcome Best Clément
Hi Clement, Thanks for taking this on! I support this fully. I've got one additional item I *really* want to try to get in to 4.1, which is the variable dds grids using non-hexahedral mesh machinery. I'm not sure it will be ready in time, but I'll give it a go. -Matt On Tue, May 31, 2022 at 10:59 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best 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
Hi all, I just wanted to issue a quick status update. While progress continues to be made, I think I was a little optimistic in my previous estimate for a completion date. Now it doesn’t seem that we’ll be able to complete the release this month. Most outstanding problems were resolved, but there are still a couple important features needing polishing and reviews. I propose we attempt to release yt 4.1 sometimes in September. We may also want to do one last bug fix release for the 4.0.x branch if needed, but I don’t think it’s warranted currently, as only a couple minor bugs were fixed since 4.0.4 Enjoy your summer, Clément
On 7 Jun 2022, at 11:46, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clement,
Thanks for taking this on! I support this fully.
I've got one additional item I *really* want to try to get in to 4.1, which is the variable dds grids using non-hexahedral mesh machinery. I'm not sure it will be ready in time, but I'll give it a go.
-Matt
On Tue, May 31, 2022 at 10:59 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best 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: clement.robert@protonmail.com
Hi Clément, Sorry for not replying sooner -- but I think especially with the things we've recently merged, and those we are close to merging, this is great. -Matt On Mon, Jul 18, 2022 at 3:10 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi all, I just wanted to issue a quick status update.
While progress continues to be made, I think I was a little optimistic in my previous estimate for a completion date. Now it doesn’t seem that we’ll be able to complete the release this month. Most outstanding problems were resolved, but there are still a couple important features needing polishing and reviews. *I propose we attempt to release yt 4.1 sometimes in September.* We may also want to do one last bug fix release for the 4.0.x branch if needed, but I don’t think it’s warranted currently, as only a couple minor bugs were fixed since 4.0.4
Enjoy your summer, Clément
On 7 Jun 2022, at 11:46, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clement,
Thanks for taking this on! I support this fully.
I've got one additional item I *really* want to try to get in to 4.1, which is the variable dds grids using non-hexahedral mesh machinery. I'm not sure it will be ready in time, but I'll give it a go.
-Matt
On Tue, May 31, 2022 at 10:59 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best 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: clement.robert@protonmail.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: matthewturk@gmail.com
Btw, update: John recently fixed an outstanding SPH bug here https://github.com/yt-project/yt/pull/4050 I think now it’d be worth considering a bugfix release for it. Clément
On 8 Aug 2022, at 19:50, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clément,
Sorry for not replying sooner -- but I think especially with the things we've recently merged, and those we are close to merging, this is great.
-Matt
On Mon, Jul 18, 2022 at 3:10 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi all, I just wanted to issue a quick status update.
While progress continues to be made, I think I was a little optimistic in my previous estimate for a completion date. Now it doesn’t seem that we’ll be able to complete the release this month. Most outstanding problems were resolved, but there are still a couple important features needing polishing and reviews. I propose we attempt to release yt 4.1 sometimes in September. We may also want to do one last bug fix release for the 4.0.x branch if needed, but I don’t think it’s warranted currently, as only a couple minor bugs were fixed since 4.0.4
Enjoy your summer, Clément
On 7 Jun 2022, at 11:46, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clement,
Thanks for taking this on! I support this fully.
I've got one additional item I *really* want to try to get in to 4.1, which is the variable dds grids using non-hexahedral mesh machinery. I'm not sure it will be ready in time, but I'll give it a go.
-Matt
On Tue, May 31, 2022 at 10:59 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best 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: clement.robert@protonmail.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: matthewturk@gmail.com
I agree with this. I'll connect with y'all on Slack to go through it. I think we have not been super-vigilant about backports since the switchover to working on 4.1. On Mon, Aug 8, 2022 at 1:01 PM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Btw, update: John recently fixed an outstanding SPH bug here https://github.com/yt-project/yt/pull/4050 I think now it’d be worth considering a bugfix release for it.
Clément
On 8 Aug 2022, at 19:50, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clément,
Sorry for not replying sooner -- but I think especially with the things we've recently merged, and those we are close to merging, this is great.
-Matt
On Mon, Jul 18, 2022 at 3:10 AM Clément Robert via yt-dev < yt-dev@python.org> wrote:
Hi all, I just wanted to issue a quick status update.
While progress continues to be made, I think I was a little optimistic in my previous estimate for a completion date. Now it doesn’t seem that we’ll be able to complete the release this month. Most outstanding problems were resolved, but there are still a couple important features needing polishing and reviews. *I propose we attempt to release yt 4.1 sometimes in September.* We may also want to do one last bug fix release for the 4.0.x branch if needed, but I don’t think it’s warranted currently, as only a couple minor bugs were fixed since 4.0.4
Enjoy your summer, Clément
On 7 Jun 2022, at 11:46, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clement,
Thanks for taking this on! I support this fully.
I've got one additional item I *really* want to try to get in to 4.1, which is the variable dds grids using non-hexahedral mesh machinery. I'm not sure it will be ready in time, but I'll give it a go.
-Matt
On Tue, May 31, 2022 at 10:59 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best 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: clement.robert@protonmail.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: 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: matthewturk@gmail.com
Hi team, October is right around the corner and we still have a couple blockers (see [the 4.1 milestone](https://github.com/yt-project/yt/milestone/17)), so it seems I again failed to predict a completion date. I don’t want to risk another prediction, but I'd advise that priority be given to resolving the remaining blocking issues. References: yt 4.1 milestone https://github.com/yt-project/yt/milestone/17 release notes (draft) https://github.com/yt-project/yt/releases/tag/untagged-51b1dba23e03eb756b18 Cheers, Clément
On 18 Jul 2022, at 10:01, Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi all, I just wanted to issue a quick status update.
While progress continues to be made, I think I was a little optimistic in my previous estimate for a completion date. Now it doesn’t seem that we’ll be able to complete the release this month. Most outstanding problems were resolved, but there are still a couple important features needing polishing and reviews. I propose we attempt to release yt 4.1 sometimes in September. We may also want to do one last bug fix release for the 4.0.x branch if needed, but I don’t think it’s warranted currently, as only a couple minor bugs were fixed since 4.0.4
Enjoy your summer, Clément
On 7 Jun 2022, at 11:46, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Clement,
Thanks for taking this on! I support this fully.
I've got one additional item I *really* want to try to get in to 4.1, which is the variable dds grids using non-hexahedral mesh machinery. I'm not sure it will be ready in time, but I'll give it a go.
-Matt
On Tue, May 31, 2022 at 10:59 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Hi team Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable. 2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17 I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best 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: clement.robert@protonmail.com
participants (2)
-
Clément Robert -
Matthew Turk