-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release documents need updating #3448
Comments
This seems crucial to release yt 4.0.2, and even if it's not, I'd like to have the information somewhere. |
@neutrinoceros and @matthewturk I think in the future we should not unassign people who have assigned themselves without a written verification that it is ok (even better is if they unassign themselves!) |
Madicken has explicitly stated that she wasn't able to work on yt for the time being (https://mail.python.org/archives/list/yt-dev@python.org/thread/4ROHTRUXH6PJJD7AHFLG4SDAD324EUUV/), which is why I took on the responsibility of unassigning her, and stepped in to try and resolve the issue. |
Yeah, I see that. I think it is great that you stepped in and assigned yourself to resolve the issue since Madicken put herself in the fallow fields. I just don't think it was necessary to unassign her. I think this issue could still be moved forward and closed without actively removing someone--if I am wrong and issues cannot be closed without removing people, definitely let me know! |
You're right, it's not blocking. I probably shouldn't have assigned myself instead, let alone Matt. |
Ooh, interesting! This is probably worth a longer discussion among more than just you and me, but I do like the idea thrown out at the end that people should only self-assign when they are starting work on something. Would definitely require some re-alignment of our use of assignments, I think. |
Okay, until that conversation happens about how yt should be using the assign feature, I am putting @munkm back on and she can stay or remove herself. |
Our release docs are out of date since we've updated our project infrastructure related to releases. We need to update the sections in the release docs to make sure these are clear.
The text was updated successfully, but these errors were encountered: