Update on yt 4.0.2: planning for what's next ?
Hi all, The 4.0.2 milestone is currently complete !https://github.com/yt-project/yt/milestone/18 I’ve switched to using the "backport-yt-4.0.x” label in PRs that are non-blocking, but could be included in the release if we’re able to merge them in time. I believe that our attempt at automating backports with MeeseekBox was a success, and it helped a lot in producing what I think is going to be the biggest bugfix release in yt’s (recent ?) history. Because this tool is most useful and reliable when used continuously (as opposed to firing 30 backport PRs at once as we did when we started using it), I suppose now is a good time to ask what’s next: do we want to go to 4.1.0, or 4.0.3 ? Since there has been no discussion about scheduling yt 4.1.0 yet, I’d suggest that we plan for an additional bugfix release (4.0.3). We don’t have to set a date for it yet, I am mostly proposing that we keep backporting bugfixes to the yt-4.0.x branch until we’re ready for a feature release. What do you think ? Take care Clément
Hi, I think we should avoid bugfix releases if possible. The question should be reversed and rather you should ask: are there any unresolved / still being developed features on main that would prevent us from cutting 4.1.0? Bugfix release only increase the maintenance burden (cause of backports, additional branches, etc). The fact that we have dozens of PRs backported is not a good thing... Cheers, Kacper On 12/14/21 5:33 PM, Clément Robert via yt-dev wrote:
Hi all,
The 4.0.2 milestone is currently complete ! https://github.com/yt-project/yt/milestone/18 <https://github.com/yt-project/yt/milestone/18>
I’ve switched to using the "backport-yt-4.0.x” label in PRs that are non-blocking, but could be included in the release if we’re able to merge them in time.
I believe that our attempt at automating backports with MeeseekBox was a success, and it helped a lot in producing what I think is going to be the biggest bugfix release in yt’s (recent ?) history. Because this tool is most useful and reliable when used continuously (as opposed to firing 30 backport PRs at once as we did when we started using it), I suppose now is a good time to ask what’s next: do we want to go to 4.1.0, or 4.0.3 ?
Since there has been no discussion about scheduling yt 4.1.0 yet, I’d suggest that we plan for an additional bugfix release (4.0.3). We don’t have to set a date for it yet, I am mostly proposing that we keep backporting bugfixes to the yt-4.0.x branch until we’re ready for a feature release. What do you think ?
Take care 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: xarthisius.kk@gmail.com
I tend to agree with this -- I think unless we have major bugs that need to be addressed and that are too important to allow for any 4.0-4.1 changes, we should focus on the future. On Wed, Dec 15, 2021 at 9:17 AM Kacper Kowalik <xarthisius.kk@gmail.com> wrote:
Hi, I think we should avoid bugfix releases if possible. The question should be reversed and rather you should ask: are there any unresolved / still being developed features on main that would prevent us from cutting 4.1.0?
Bugfix release only increase the maintenance burden (cause of backports, additional branches, etc). The fact that we have dozens of PRs backported is not a good thing...
Cheers, Kacper
On 12/14/21 5:33 PM, Clément Robert via yt-dev wrote:
Hi all,
The 4.0.2 milestone is currently complete ! https://github.com/yt-project/yt/milestone/18 <https://github.com/yt-project/yt/milestone/18>
I’ve switched to using the "backport-yt-4.0.x” label in PRs that are non-blocking, but could be included in the release if we’re able to merge them in time.
I believe that our attempt at automating backports with MeeseekBox was a success, and it helped a lot in producing what I think is going to be the biggest bugfix release in yt’s (recent ?) history. Because this tool is most useful and reliable when used continuously (as opposed to firing 30 backport PRs at once as we did when we started using it), I suppose now is a good time to ask what’s next: do we want to go to 4.1.0, or 4.0.3 ?
Since there has been no discussion about scheduling yt 4.1.0 yet, I’d suggest that we plan for an additional bugfix release (4.0.3). We don’t have to set a date for it yet, I am mostly proposing that we keep backporting bugfixes to the yt-4.0.x branch until we’re ready for a feature release. What do you think ?
Take care 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: xarthisius.kk@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
I don’t currently know of any blocker, I guess it’d be fine to not do any release for a couple month and going straight to 4.1. I would be perfectly fine with it, I’m just mostly interested in balancing dev pressure (or maintenance burden) with a reasonable delivery pace for users. What do you guys think could be a reasonable time window before we can do a 4.1 ?
On 15 Dec 2021, at 16:19, Matthew Turk <matthewturk@gmail.com> wrote:
I tend to agree with this -- I think unless we have major bugs that need to be addressed and that are too important to allow for any 4.0-4.1 changes, we should focus on the future.
On Wed, Dec 15, 2021 at 9:17 AM Kacper Kowalik <xarthisius.kk@gmail.com> wrote:
Hi, I think we should avoid bugfix releases if possible. The question should be reversed and rather you should ask: are there any unresolved / still being developed features on main that would prevent us from cutting 4.1.0?
Bugfix release only increase the maintenance burden (cause of backports, additional branches, etc). The fact that we have dozens of PRs backported is not a good thing...
Cheers, Kacper
On 12/14/21 5:33 PM, Clément Robert via yt-dev wrote:
Hi all,
The 4.0.2 milestone is currently complete ! https://github.com/yt-project/yt/milestone/18 <https://github.com/yt-project/yt/milestone/18>
I’ve switched to using the "backport-yt-4.0.x” label in PRs that are non-blocking, but could be included in the release if we’re able to merge them in time.
I believe that our attempt at automating backports with MeeseekBox was a success, and it helped a lot in producing what I think is going to be the biggest bugfix release in yt’s (recent ?) history. Because this tool is most useful and reliable when used continuously (as opposed to firing 30 backport PRs at once as we did when we started using it), I suppose now is a good time to ask what’s next: do we want to go to 4.1.0, or 4.0.3 ?
Since there has been no discussion about scheduling yt 4.1.0 yet, I’d suggest that we plan for an additional bugfix release (4.0.3). We don’t have to set a date for it yet, I am mostly proposing that we keep backporting bugfixes to the yt-4.0.x branch until we’re ready for a feature release. What do you think ?
Take care 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: xarthisius.kk@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
_______________________________________________ yt-dev mailing list --yt-dev@python.org To unsubscribe send an email toyt-dev-leave@python.org https://mail.python.org/mailman3/lists/yt-dev.python.org/ Member address:clement.robert@protonmail.com
Hi Clement, That's a good question. (Also, I will note that the AREPO bug John ZuHone reported would be worth a point release.) I'm working on writing some of this down right now, but I see a few major projects underway, and I'm going to try to break them down into "github projects" and whatnot to progress. In fact, I'm attempting to address that right now ... I'll follow up to this list when I get them written up. -Matt On Wed, Dec 15, 2021 at 9:27 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
I don’t currently know of any blocker, I guess it’d be fine to not do any release for a couple month and going straight to 4.1. I would be perfectly fine with it, I’m just mostly interested in balancing dev pressure (or maintenance burden) with a reasonable delivery pace for users. What do you guys think could be a reasonable time window before we can do a 4.1 ?
On 15 Dec 2021, at 16:19, Matthew Turk <matthewturk@gmail.com> wrote:
I tend to agree with this -- I think unless we have major bugs that need to be addressed and that are too important to allow for any 4.0-4.1 changes, we should focus on the future.
On Wed, Dec 15, 2021 at 9:17 AM Kacper Kowalik <xarthisius.kk@gmail.com> wrote:
Hi, I think we should avoid bugfix releases if possible. The question should be reversed and rather you should ask: are there any unresolved / still being developed features on main that would prevent us from cutting 4.1.0?
Bugfix release only increase the maintenance burden (cause of backports, additional branches, etc). The fact that we have dozens of PRs backported is not a good thing...
Cheers, Kacper
On 12/14/21 5:33 PM, Clément Robert via yt-dev wrote:
Hi all,
The 4.0.2 milestone is currently complete ! https://github.com/yt-project/yt/milestone/18 <https://github.com/yt-project/yt/milestone/18>
I’ve switched to using the "backport-yt-4.0.x” label in PRs that are non-blocking, but could be included in the release if we’re able to merge them in time.
I believe that our attempt at automating backports with MeeseekBox was a success, and it helped a lot in producing what I think is going to be the biggest bugfix release in yt’s (recent ?) history. Because this tool is most useful and reliable when used continuously (as opposed to firing 30 backport PRs at once as we did when we started using it), I suppose now is a good time to ask what’s next: do we want to go to 4.1.0, or 4.0.3 ?
Since there has been no discussion about scheduling yt 4.1.0 yet, I’d suggest that we plan for an additional bugfix release (4.0.3). We don’t have to set a date for it yet, I am mostly proposing that we keep backporting bugfixes to the yt-4.0.x branch until we’re ready for a feature release. What do you think ?
Take care 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: xarthisius.kk@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
_______________________________________________ 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
participants (3)
-
Clément Robert -
Kacper Kowalik -
Matthew Turk