Closed jrbourbeau closed 2 years ago
One high level question that comes up when considering this is how we manage requests for releases (since these come up periodically) and separate them from release tracking?
That's a fair point. This doesn't happen that often, but you're right that it does come up from time to time. Maybe open a community issue still with the release request and then the release manager opens up a tracking issue? Do you have thoughts on a process here?
Yeah that seems fine
We may also want to note in this template or in the issue selection GUI that this is intended for release managers only (and requests for a release should be a new issue)
We may also want to note in this template or in the issue selection GUI that this is intended for release managers only (and requests for a release should be a new issue)
I updated the about
section of the template to mention release managers and added a comment to the template which says the template is explicitly for release managers and if someone wants to request a new release, they should open a different issue in the dask/community
repo
Thanks @jakirkham @jsignell for reviewing!
I'm fine with trying this out. We can always tweak it as we go.
+1
Closes https://github.com/dask/community/issues/247
cc @fjetter @jakirkham @jsignell @jacobtomlinson