-
Notifications
You must be signed in to change notification settings - Fork 210
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 upgrade docs in RELEASE_PROCESS.md. #789
Conversation
19694b0
to
d77b8f4
Compare
- The CHANGELOG_GITHUB_TOKEN environment variable set to a github token gathered here: https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token | ||
- Install Github Changelog Generator: `gem install github_changelog_generator` | ||
- The CHANGELOG_GITHUB_TOKEN environment variable set to a github token gathered | ||
[here](https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token). |
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.
What permissions do I need to give it? So far, I gave it read access to repos/commits - I haven't gone far enough through the checklist to know if that's enough.
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.
No idea :D been trying to get more clarity on that myself.
FYI - @marcparadise had another PR: #722 updating some post release steps. I'm keeping both of these in mind throughout the release process. By the time this release is done, I figure we'll have enough evidence to validate both of these PRs and merge them both. |
@@ -24,33 +24,71 @@ In order to release, you will need the following accounts/permissions: | |||
- Chef Software, Inc Slack account | |||
- blog.chef.io wordpress account |
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.
you don't need a blog account now, you now need a discourse account set up with your chef.io email address so discourse automatically adds you to the Chef staff group.
https://www.chef.io/blog/2016/03/29/moving-release-and-security-announcements-to-discourse/
Can you change:
to:
please? |
@ksubrama all aboard the merge conflict 🚂! |
#795 has been merged, which adds updates for the new release announcements to discourse and adds a note on #cft-announce being the proper place for internal announcements. |
👍 Thanks for making those changes! |
e61e211
to
71b914f
Compare
71b914f
to
f645e6b
Compare
Rebased and merged! Thanks all. |
No description provided.