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

Update upgrade docs in RELEASE_PROCESS.md. #789

Merged
merged 2 commits into from
Apr 1, 2016

Conversation

tylercloke
Copy link
Contributor

No description provided.

- 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).

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.

Copy link
Contributor Author

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.

@ksubrama
Copy link

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
Copy link
Contributor

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/

@btm
Copy link
Contributor

btm commented Mar 29, 2016

Can you change:

  • Publish your draft blog post.

to:

  • Publish your draft post in the 'Chef Release Announcements' category on Discourse

please?

@ksubrama
Copy link

@btm I think #795 has the changes your want :)

@ksubrama
Copy link

@mmzyk @jmink

@btm
Copy link
Contributor

btm commented Apr 1, 2016

@ksubrama all aboard the merge conflict 🚂!

@mmzyk
Copy link
Contributor

mmzyk commented Apr 1, 2016

#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.

@jmink
Copy link
Contributor

jmink commented Apr 1, 2016

👍 Thanks for making those changes!

@ksubrama ksubrama force-pushed the tc/update-upgrade-testing-docs branch from e61e211 to 71b914f Compare April 1, 2016 18:59
@ksubrama ksubrama force-pushed the tc/update-upgrade-testing-docs branch from 71b914f to f645e6b Compare April 1, 2016 19:33
@ksubrama
Copy link

ksubrama commented Apr 1, 2016

Rebased and merged! Thanks all.

@ksubrama ksubrama merged commit d1cd9c7 into master Apr 1, 2016
@ksubrama ksubrama deleted the tc/update-upgrade-testing-docs branch April 1, 2016 19:33
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.

7 participants