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

Keep a CHANGELOG #3

Merged
merged 1 commit into from
Jul 18, 2016
Merged

Keep a CHANGELOG #3

merged 1 commit into from
Jul 18, 2016

Conversation

fiveop
Copy link
Contributor

@fiveop fiveop commented Jul 13, 2016

[design]: #detailed-design

We follow the conventions laid out in [Keep A CHANGELOG](https://github.com/olivierlacan/keep-a-changelog/tree/18adb5f5be7a898d046f6a4acb93e39dcf40c4ad).

Copy link
Member

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.

Copy link
Member

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.

@posborne
Copy link
Member

Looks good generally.

@fiveop
Copy link
Contributor Author

fiveop commented Jul 15, 2016

Thank you, for the feedback. I already added, that we create an initial CHANGELOG.md.

@fiveop
Copy link
Contributor Author

fiveop commented Jul 15, 2016

r? @kamalmarhubi

@kamalmarhubi
Copy link
Member

kamalmarhubi commented Jul 17, 2016

Sorry for the general slowness lately!

@kamalmarhubi
Copy link
Member

Yeah I like this.

@fiveop
Copy link
Contributor Author

fiveop commented Jul 18, 2016

Given, that I addressed everything @posborne brought up, and @kamalmarhubi did not have any concerns, we (someone) should merge this.

@posborne
Copy link
Member

@homu r+

@posborne
Copy link
Member

Looks like @kamalmarhubi will have to hit Merge.

@kamalmarhubi
Copy link
Member

Will have to tinker with permissions...

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.

3 participants