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

docs(all): update release instructions #3107

Merged
merged 4 commits into from Oct 29, 2020
Merged

docs(all): update release instructions #3107

merged 4 commits into from Oct 29, 2020

Conversation

codyoss
Copy link
Member

@codyoss codyoss commented Oct 29, 2020

No description provided.

@codyoss codyoss requested a review from a team as a code owner October 29, 2020 14:52
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Oct 29, 2020
RELEASING.md Outdated
automatically opened with a title like "chore: release 0.XX.0", where XX is the
next version to be released. To cut a release approve and merge this pull
request. Doing so will update the `CHANGES.md`, tag the merged commit with the
appropriate version , and draft a GitHub release.
Copy link
Contributor

Choose a reason for hiding this comment

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

Draft? Does the person doing the release need to do anything?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think the is the terminology used for releases. The button in Github to do this is Draft a release. And nope, it is done automagically. Here is an example of an automated github release: https://github.com/googleapis/google-cloud-go/releases/tag/v0.70.0

RELEASING.md Outdated Show resolved Hide resolved
RELEASING.md Outdated

### Automated Release

If there are changes that have not yet been released a pull request should be
Copy link
Contributor

Choose a reason for hiding this comment

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

Specify a PR from release-please? Link to those docs?

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like this change wasn't uploaded?

RELEASING.md Show resolved Hide resolved
RELEASING.md Show resolved Hide resolved
Co-authored-by: Tyler Bui-Palsulich <26876514+tbpg@users.noreply.github.com>
@codyoss codyoss requested a review from tbpg October 29, 2020 18:24
RELEASING.md Outdated
automatically opened with a title like "chore: release 0.XX.0", where XX is the
next version to be released. To cut a release, approve and merge this pull
request. Doing so will update the `CHANGES.md`, tag the merged commit with the
appropriate version , and draft a GitHub release.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
appropriate version , and draft a GitHub release.
appropriate version, and draft a GitHub release.

RELEASING.md Outdated

### Automated Release

If there are changes that have not yet been released a pull request should be
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like this change wasn't uploaded?

@codyoss
Copy link
Member Author

codyoss commented Oct 29, 2020

They are live now, turns out it helps if you git push 😄

@codyoss codyoss merged commit 737aa66 into googleapis:master Oct 29, 2020
@codyoss codyoss deleted the release-update branch October 29, 2020 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants