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

Added docs explaining how to cut a collins release #503

Merged
merged 1 commit into from Jan 11, 2017

Conversation

william-richard
Copy link
Contributor

@tumblr/collins RFR

- [ ] Check out the collins code in an environment running jdk 7 with the unlimited strength JCE configured correctly, and play activator checked out in the correct location (`$HOME/src/activator-1.3.6-minimal/activator`). Run `scripts/package.sh` and attach the resulting zip to the release, and name it `collins-v<version number>.zip`.
- [ ] Do the previous step but in an environment with jdk 8. Attach the zip to the release, and title it `collins-v<version number>-jdk8.zip`.
- [ ] Save, but do not publish, the draft. If you want to get proofreading for your release text, this is the right time to do it.
- [ ] Cut a new branch off of master. Copy the text of the release into the [CHANGELOG.md](https://github.com/tumblr/collins/blob/master/CHANGELOG.md) file. Open a PR and get thumbs. See https://github.com/tumblr/collins/pull/490 for an example PR.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this step be removed if we are moving to github Release only?
I see that you say so below. Lets just drop CHANGELOG.md on the next release!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I left it in there since I likely will not be running the next release - if that's the way we want to go, then whomever is doing it next can make those changes.

Copy link
Contributor

@roymarantz roymarantz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good.
I'd propose we remove CHANGELOG.md and have someone who hasn't cut a release check do so following these instructions to make sure they have enough detail

@william-richard william-richard merged commit 61a4117 into master Jan 11, 2017
@william-richard william-richard deleted the will-document-release-process branch January 11, 2017 16:15
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.

None yet

3 participants