go-ethereum/docs/Release-Process.md

Release process for Swarm

This document describes the steps required to perform a new release.

Pre release

1. Make sure that the most recent builds are green and that smoke tests are passing on the cluster.
2. Check if protocols should be bumped. (e.g PR#1465)
3. Check if the CHANGELOG.md is reflecting all the changes.

Release

1. Create a PR to update version.go and CHANGELOG.md. See example PR.
2. Merge the PR after all tests passed.
3. Tag the merged commit that went into master.

git checkout master
git pull
git tag v0.4.{x}
git push origin v0.4.{x}

4. CI Builds (Travis/Appveyor/DockerHub) will trigger. Wait for them to finish.
5. Verify that the following places have the new release:
   1. Website download page
   2. Docker Hub
   3. Ubuntu PPA
6. Create a PR to update version.go and CHANGELOG.md, this time setting it to unstable and increasing the version number: See example PR.
7. Merge the PR after all tests passed.
8. Close the milestone.

Post release

1. Update bootnodes and the nodes serving swarm-gateways.net
2. Announce the release on social media:
   1. Create post on reddit: https://www.reddit.com/r/ethswarm/
   2. Share post on gitter: ethersphere/orange-lounge and ethereum/swarm