Release v0.14 #9032
Comments
guseggert
added
topic/release
|
Placeholder |
|
When we have |
|
Let's collect release template improvements here: #9100 |
|
@Jorropo : concerning the Kubo 0.14 release, I’ve been thinking on this more. I think we should prioritize seeing if we can get this change out this week (week of 2022-07-18) because it is holding up the big docs change (ipfs/ipfs-docs#1185 ), and I expect various folks are going to want to make docs changes as a result of the IPFS Thing event. Understood if you’re needing to take some rest time. When you’re not resting, I’d like to prioritize this by:
Sound good and make sense? |
|
Below is the state of the "0.14" iteration before we started 0.15:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
go-ipfs 0.14.0 Release
We're happy to announce go-ipfs 0.14.0, bla bla...
As usual, this release includes important fixes, some of which may be critical for security. Unless the fix addresses a bug being exploited in the wild, the fix will not be called out in the release notes. Please make sure to update ASAP. See our release process for details.
🗺 What's left for release
🚢 Estimated shipping date
RC: week of 2022-07-04 (2022-07-07)
Final release: 2022-07-20
🔦 Highlights
< top highlights for this release notes >
✅ Release Checklist
Before doing the following:
For each RC published in each stage:
version.gohas been updated (in therelease-vX.Y.Zbranch).release-vX.Y.Zbranch frommasterusinggit cherry-pick -x ...vX.Y.Z-rcNChecklist:
release-vX.Y.Z) frommasterand make any further release related changes to this branch. If any "non-trivial" changes (see the footnotes of docs/releases.md for a definition) get added to the release, uncheck all the checkboxes and return to this stage.version.goin themasterbranch tovX.(Y+1).0-dev.make test)make test_go_lint)./bin/mkreleaselogto generate a nice starter listversion.gohas been updated.release-vX.Y.Zinto thereleasebranch.go-ipfs.releasebranch) withvX.Y.Z.git tag -sto ensure the tag is signedgo-ipfs(This has been done with one single person since I made two versions back to back, is that ok in the future ?)
git push origin <tag>git push --tags, as it will push ALL of your local tagsvX.Y.Ztagged Docker image to DockerHubgo-ipfstokuboipfs-docs#1185releasebranch back intomaster, ignoring the changes toversion.go(keep the-devversion from master).The best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the
#ipfschannel on Freenode, which is also accessible through our Matrix bridge.Release improvements for next time
< Add any release improvements that were observed this cycle here so they can get incorporated into future releases. >
Items for a separate comment
< Do these as a separate comment to avoid the main issue from getting too large and checkbox updates taking too long. >
Changelog
< changelog generated by bin/mkreleaselog >
❤️ Contributors
< list generated by bin/mkreleaselog >
Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:
help wantedlabel in the go-ipfs repoThe text was updated successfully, but these errors were encountered: