coosld/kubo
1
0
Fork 0
mirror of https://github.com/ipfs/kubo.git synced 2026-02-23 11:27:42 +08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
fb414229f9
kubo/docs/releases.md
Steven Allen 1c70c5c5cf document the fact that we now publish releases on GitHub 
(due to censorship of ipfs.io)

License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>
2018-07-28 15:38:42 -07:00

2.1 KiB
Raw Blame History

go-ipfs releases

Release Schedule

go-ipfs is on a six week release schedule. Following a release, there will be five weeks for code of any type (features, bugfixes, etc) to be added. After the five weeks is up, a release candidate is tagged and only important bugfixes will be allowed up to release day.

Release Candidate Checklist

  • CHANGELOG.md has been updated
    • use ./bin/mkreleaselog to generate a nice starter list
  • version string in repo/config/version.go has been updated
  • tag commit with vX.Y.Z-rcN
  • publish gx version with gx publish, as per gx release guidelines
    • you will have to manually adjust the gx version to 'rc'

Pre-Release Checklist

  • before release, tag 'release candidate' for users to test against
    • if bugs are found/fixed, do another release candidate
  • all tests pass (no exceptions)
  • run interop tests https://github.com/ipfs/interop#test-with-a-non-yet-released-version-of-go-ipfs
  • webui works (for most definitions of 'works') - Test the multiple pages and verify that no visible errors are shown.
  • CHANGELOG.md has been updated
    • use ./bin/mkreleaselog to generate a nice starter list
  • version string in repo/config/version.go has been updated
  • tag commit with vX.Y.Z
  • update release branch to point to release commit
  • publish dist.ipfs.io
  • publish next version to https://github.com/ipfs/npm-go-ipfs
  • publish gx version with gx release, as per gx release guidelines

Post-Release

  • Bump version string in repo/config/version.go to vX.Y.Z-dev
  • Upload the final release to the github releases page: https://github.com/ipfs/go-ipfs/releases
  • Communication
    • Create the release issue
    • Announcements (both pre-release and post-release)
      • Twitter
      • IRC
      • Reddit
    • Blog post (at minimum, paste the changelog. optionally add context and thank contributors.)
  • Update HTTP-API Documentation on the Website using https://github.com/ipfs/http-api-docs