Skip to content

MINOR: create a checklist for testing a new Storm release#3161

Merged
Ethanlm merged 2 commits into
apache:masterfrom
Ethanlm:update-release-doc-2
Oct 31, 2019
Merged

MINOR: create a checklist for testing a new Storm release#3161
Ethanlm merged 2 commits into
apache:masterfrom
Ethanlm:update-release-doc-2

Conversation

@Ethanlm
Copy link
Copy Markdown
Contributor

@Ethanlm Ethanlm commented Oct 30, 2019

This creates a checklist so new devs have a better idea on reviewing a release

@Ethanlm Ethanlm force-pushed the update-release-doc-2 branch from 9258256 to 459cd58 Compare October 30, 2019 16:38
@Ethanlm Ethanlm force-pushed the update-release-doc-2 branch from 459cd58 to b01bc8e Compare October 30, 2019 16:42
Comment thread RELEASING.md Outdated
Below is a checklist that one could do to review a release candidate.
Please note this list is not exhaustive and only includes some of the common steps. Feel free to add your own tests.

1. Verify files such as *.asc, *.sha512;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think we should link to the utility script in dev-tools/rc for this. I didn't know about it until I happened across it recently, would be good to raise visibility.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think the original order is fine. We need to have release candidate then we can review and vote. It's more natural to me

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think your comments got switched somehow.

Ok, it's fine. I'd just like this guidance to be visible to people.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ah.. my bad

Comment thread RELEASING.md

3. Delete the git tag.

# How to vote on a release candidate
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm wondering if this belongs at the top of the file? The audience for it is probably broader than the audience for how to author a release.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

make sense

@srdo
Copy link
Copy Markdown
Contributor

srdo commented Oct 31, 2019

+1

@Ethanlm Ethanlm merged commit 4c69b96 into apache:master Oct 31, 2019
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.

2 participants