In general for a release we want to:
- Describe the features in the release to the community (prior to cutting release)
- Forum: Community hangout
- Review documentation about the release (release readiness review)
- Demo.
- Create a package for download
- Create an AWS docker image (at some point)
- Create a release version in the code repository, this could be a release branch, or a tag
- Provide documentation as part of the package (and image)
- Provide a channel for communicating about the release, file bugs, etc..
- Gitter channels
Storage:
- Alternative is to create a tag + build on master with all of the RChain binaries. (this does offer a side benefit of putting everything on the dev's machine) - need to find out if this is a desirable UX or not.
- Use Git releases
- Meet with the community and present the release
- Documentation
- Demo of features
- Code walk through
- Create a tag on Master & label it Storage.01
- Gitter channels - TBD - Storage only or RChain collective.
- Git release for builts
- Small splash
Roscala:
- Merge to master
- Meet with community to review the update
- Create release tag & label with the name of the release.
- Use Git releases to distribute any binaries
For Roscala.Void
- Merge to master
- Code walk through?
- Create tag 'Roscala.Void' on master