Skip to content
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-Managers: Make ongoing conflicts a criteria #85

Merged
merged 1 commit into from
Apr 27, 2024

Conversation

mweinelt
Copy link
Member

The release manager role is primarily one that is about communication. If a release manager would be part of an ongoing conflict it could prevent them from effectively communicating with various maintainers on nixpkgs.

There is also a chance it coudl taint and potentially overshadow the release process, a risk that should be mitigated early on.

The release manager role is primarily one that is about communication. If
a release manager would be part of an ongoing conflict it could prevent
them from effectively communicating with various maintainers on nixpkgs.

There is also a chance it coudl taint and potentially overshadow the
release process, a risk that should be mitigated early on.
Copy link
Member

@dasJ dasJ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both argument and reasoning make sense to me, let's see how well this will work in practice 🚀

@wegank wegank merged commit 595a6a3 into NixOS:master Apr 27, 2024
1 check passed
@mweinelt mweinelt deleted the release-manager-conflict branch April 27, 2024 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants