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

Create PATCH_RELEASE_TEMPLATE #8282

Merged
merged 1 commit into from
Jul 21, 2021
Merged

Conversation

aschmahmann
Copy link
Contributor

No description provided.

@aschmahmann aschmahmann changed the title create PATCH_RELEASE_TEMPLATE Create PATCH_RELEASE_TEMPLATE Jul 20, 2021
This process handles patch releases from version `vX.Y.Z` to `vX.Y.Z+1` assuming that `vX.Y.Z` is the latest released version of go-ipfs.

- [ ] Fork a new branch (`release-vX.Y.Z`) from `release` and cherry-pick the relevant commits from master (or custom fixes) onto this branch
- [ ] Make a minimal changelog update tracking the relevant fixes to CHANGELOG.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was thinking to just make this free hand and look something like #8267 (comment) instead of something more formal or using mkreleaselog. Thoughts?

@aschmahmann
Copy link
Contributor Author

I didn't add a section for testing here. For v0.9.1 the testing was mostly ad hoc to see if the immediate issues were solved. Should anything more formal be here, it seems like it depends on how long we're ok waiting for a patch release.

2. Pin the resulting release.
3. Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
4. Ask the infra team to update the DNSLink record for dist.ipfs.io to point to the new distribution.
- [ ] cut a release on [github](https://github.com/ipfs/go-ipfs/releases) and upload the result of the ipfs/distributions build in the previous step.
Copy link
Member

Choose a reason for hiding this comment

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

Hm. The duplication here is a bit annoying, but not terrible.

@aschmahmann aschmahmann merged commit 74bd44f into master Jul 21, 2021
@BigLep BigLep linked an issue Jul 21, 2021 that may be closed by this pull request
@hacdias hacdias deleted the docs/patch-release-template branch May 9, 2023 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Write a patch release template
2 participants