-
Notifications
You must be signed in to change notification settings - Fork 3
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
Keep a CHANGELOG #3
Conversation
[design]: #detailed-design | ||
|
||
We follow the conventions laid out in [Keep A CHANGELOG](https://github.com/olivierlacan/keep-a-changelog/tree/18adb5f5be7a898d046f6a4acb93e39dcf40c4ad). | ||
|
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.
Might be useful to include the following:
- Guidlines for contributors related to updating the changelog (probably encourage it but make it a soft requirement)
- Note responsibility for maintainer to update CHANGELOG before release including creating a new unreleased section.
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.
Guidlines for contributors related to updating the changelog (probably encourage it but make it a soft requirement)
👍 to that. We don't want it to block people from contributing, so maintainers can always fix it up later.
Looks good generally. |
Thank you, for the feedback. I already added, that we create an initial CHANGELOG.md. |
Sorry for the general slowness lately! |
Yeah I like this. |
Given, that I addressed everything @posborne brought up, and @kamalmarhubi did not have any concerns, we (someone) should merge this. |
@homu r+ |
Looks like @kamalmarhubi will have to hit Merge. |
Will have to tinker with permissions... |
See nix-rust/nix#363