Hi yt dev! It has been some time since we last did a release of yt. `master` has a lot of features that are not in any of our releases on pypi and conda forge. We're also prepping for the yt-4.0 release soon. I propose that we try to get yt 3.6 out the door soon so we can use our developer time on yt-4.0. We should leave some time so that people can get issues resolved and minor features added before we publish the release. Is April 08 a long enough time out for everybody? If not, what would be better? That's just under two weeks out, but the release would happen on a Wednesday so we have a couple of days to put out fires if things go horribly wrong (and we're not working over a weekend). What do you think? Is this too aggressive? Too slow? I've added a label to the yt repo called `yt-3.6`. Please use this label (or comment if you don't have access to the labels) in your open PRs or in your PRs that you submit before we do the release if you want them to be included in yt-3.6. For the next while we'll prioritize review of the 3.6 related PRs. The CI platforms are still not reliably running on master. I'll do my best to get them working ASAP so we know that the features we're adding aren't introducing obvious breaking changes. -Madicken TL;DR: - I am proposing we release the yt 3.6 on April 08. Do you all agree on this timeline? - If you want to have a feature in yt 3.6 or resolve an issue before this release, please label using the yt-3.6 label or comment in your PRs that this is a yt 3.6 feature. We will give review priority to those PRs before the release.
Hi Madicken, Thank you, this is awesome. I agree on this timeline. On Fri, Mar 27, 2020 at 10:55 AM Madicken Munk <madicken.munk@gmail.com> wrote:
Hi yt dev!
It has been some time since we last did a release of yt. `master` has a lot of features that are not in any of our releases on pypi and conda forge. We're also prepping for the yt-4.0 release soon. I propose that we try to get yt 3.6 out the door soon so we can use our developer time on yt-4.0. We should leave some time so that people can get issues resolved and minor features added before we publish the release. Is April 08 a long enough time out for everybody? If not, what would be better? That's just under two weeks out, but the release would happen on a Wednesday so we have a couple of days to put out fires if things go horribly wrong (and we're not working over a weekend). What do you think? Is this too aggressive? Too slow?
I've added a label to the yt repo called `yt-3.6`. Please use this label (or comment if you don't have access to the labels) in your open PRs or in your PRs that you submit before we do the release if you want them to be included in yt-3.6. For the next while we'll prioritize review of the 3.6 related PRs.
The CI platforms are still not reliably running on master. I'll do my best to get them working ASAP so we know that the features we're adding aren't introducing obvious breaking changes.
-Madicken
TL;DR: - I am proposing we release the yt 3.6 on April 08. Do you all agree on this timeline? - If you want to have a feature in yt 3.6 or resolve an issue before this release, please label using the yt-3.6 label or comment in your PRs that this is a yt 3.6 feature. We will give review priority to those PRs before the release.
-- You received this message because you are subscribed to the Google Groups "yt-exec" group. To unsubscribe from this group and stop receiving emails from it, send an email to yt-exec+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/yt-exec/CACZp%2BDH%2BSYEkLRf25U%2BrGdMFw4O....
Super +1 on this. On Fri, Mar 27, 2020 at 6:27 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi Madicken,
Thank you, this is awesome. I agree on this timeline.
On Fri, Mar 27, 2020 at 10:55 AM Madicken Munk <madicken.munk@gmail.com> wrote:
Hi yt dev!
It has been some time since we last did a release of yt. `master` has a
lot of features that are not in any of our releases on pypi and conda forge. We're also prepping for the yt-4.0 release soon. I propose that we try to get yt 3.6 out the door soon so we can use our developer time on yt-4.0. We should leave some time so that people can get issues resolved and minor features added before we publish the release. Is April 08 a long enough time out for everybody? If not, what would be better? That's just under two weeks out, but the release would happen on a Wednesday so we have a couple of days to put out fires if things go horribly wrong (and we're not working over a weekend). What do you think? Is this too aggressive? Too slow?
I've added a label to the yt repo called `yt-3.6`. Please use this label
(or comment if you don't have access to the labels) in your open PRs or in your PRs that you submit before we do the release if you want them to be included in yt-3.6. For the next while we'll prioritize review of the 3.6 related PRs.
The CI platforms are still not reliably running on master. I'll do my
best to get them working ASAP so we know that the features we're adding aren't introducing obvious breaking changes.
-Madicken
TL;DR: - I am proposing we release the yt 3.6 on April 08. Do you all agree on
- If you want to have a feature in yt 3.6 or resolve an issue before
this timeline? this release, please label using the yt-3.6 label or comment in your PRs that this is a yt 3.6 feature. We will give review priority to those PRs before the release.
-- You received this message because you are subscribed to the Google
Groups "yt-exec" group.
To unsubscribe from this group and stop receiving emails from it, send an email to yt-exec+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/yt-exec/CACZp%2BDH%2BSYEkLRf25U%2BrGdMFw4O... .
yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
This seems great! It will be great to get this out the door. On Fri, Mar 27, 2020 at 11:45 AM Britton Smith <brittonsmith@gmail.com> wrote:
Super +1 on this.
On Fri, Mar 27, 2020 at 6:27 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi Madicken,
Thank you, this is awesome. I agree on this timeline.
On Fri, Mar 27, 2020 at 10:55 AM Madicken Munk <madicken.munk@gmail.com> wrote:
Hi yt dev!
It has been some time since we last did a release of yt. `master` has a
lot of features that are not in any of our releases on pypi and conda forge. We're also prepping for the yt-4.0 release soon. I propose that we try to get yt 3.6 out the door soon so we can use our developer time on yt-4.0. We should leave some time so that people can get issues resolved and minor features added before we publish the release. Is April 08 a long enough time out for everybody? If not, what would be better? That's just under two weeks out, but the release would happen on a Wednesday so we have a couple of days to put out fires if things go horribly wrong (and we're not working over a weekend). What do you think? Is this too aggressive? Too slow?
I've added a label to the yt repo called `yt-3.6`. Please use this
label (or comment if you don't have access to the labels) in your open PRs or in your PRs that you submit before we do the release if you want them to be included in yt-3.6. For the next while we'll prioritize review of the 3.6 related PRs.
The CI platforms are still not reliably running on master. I'll do my
best to get them working ASAP so we know that the features we're adding aren't introducing obvious breaking changes.
-Madicken
TL;DR: - I am proposing we release the yt 3.6 on April 08. Do you all agree on
- If you want to have a feature in yt 3.6 or resolve an issue before
this timeline? this release, please label using the yt-3.6 label or comment in your PRs that this is a yt 3.6 feature. We will give review priority to those PRs before the release.
-- You received this message because you are subscribed to the Google
Groups "yt-exec" group.
To unsubscribe from this group and stop receiving emails from it, send an email to yt-exec+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/yt-exec/CACZp%2BDH%2BSYEkLRf25U%2BrGdMFw4O... .
yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org
participants (4)
-
Britton Smith -
Cameron Hummels -
Madicken Munk -
Matthew Turk