-
Notifications
You must be signed in to change notification settings - Fork 24
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
Update governance guidelines #105
Conversation
GOVERNANCE.md
Outdated
@@ -33,12 +35,13 @@ A PR should be created with all relevant changes to update the repository for th | |||
It should apply the following actions: | |||
|
|||
1. Change the "Unreleased version" heading in the CHANGELOG.md file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Upcoming version" works for me as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 1a9ae64 :)
@@ -33,12 +35,13 @@ A PR should be created with all relevant changes to update the repository for th | |||
It should apply the following actions: | |||
|
|||
1. Change the "Unreleased version" heading in the CHANGELOG.md file | |||
to the appropriate version name (e.g. "Version 1.2.3") | |||
and add a new "Unreleased version" section heading above it; | |||
to the appropriate version name and date (e.g. "Version 1.2.3 - 2020-12-31") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really biased either way, but if you are splitting off commits from #102 anyway, I'm fine with that commit going into this PR too. Along with the initial header change per my comment above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't cleanly cherry-pick that commit into this branch, because it includes adding the section header for the new release (which should remain in #102), but I'll recreate the parts that need to be moved and will mark you as co-author of the commit :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine, if I need to make changes to my branch locally, and pull/push stuff around, please detail any steps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, no worries. In fact, I should be able to update your branch myself. Then, if it looks good to you on GitHub, you will be able to pull the updated branch to your local clone as well.
No further comments on the committed changes, they look fine to me. |
For when only one maintainer is available.
Co-authored-by: Xymph <Xymph@users.noreply.github.com>
c928b02
to
e6735a2
Compare
OK, changes made. Please check the updated commits. I've updated the PR description as well. |
Almost everything looks fine to me, the only previous change I don't see anymore is the formatting of Btw, remember to add #105 to the Changelog for v0.13.0. |
The formatting reversal was intentional — the other filenames in that document are not code-formatted, so I reverted it for consistency. I can change them all to be code-formatted, though. As for adding a changelog entry — OMG, of course! I'll add a new commit for that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
16c8d28 looking good now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I forgot we could combine multiple PRs into the same entry. Will change. |
16c8d28
to
2e771cd
Compare
Great, looks ready to wrap up. |
Great :) Please go ahead at your convenience. |
See the relevant discussions in #102 for context.