This document describe the process of making releases. Some of this position may be automated but currently is not done.
-
Assumptions:
- Every branch/feature pushes the description
.mdfile into.releasedirectory.
- Every branch/feature pushes the description
-
Locally:
- Merge everything needed into
developbranch. Run tests. - Update changelog using script
.release/updateChangelog.shspecifying the version as a parameter. You need to be in.releasedirectory to do that.- Also update the release log with extra information coming not from branches.
- Change the order of the entries if necessary.
- Update the root
README.mdfile with the link to new version on Bintray. - Update
versioningradle.properties. - Commit with message
Release $VERSION. - Tag the current commit and push it.
- Merge everything needed into
-
Bintray:
- Upload new version:
./gradlew bintrayUpload -Pversion=$VERSION -Pbintray.user=$USER -Pbintray.key=$KEY
- Goto bintray.com, choose the wavebeans organization and publish artifacts.
- Upload new version of cli tool:
- build locally via
./gradlew distTar distZip - on Bintray, select version, then
Actions > Upload Files. Uploadcli/build/distributions/*.*
- build locally via
-
GitHub:
- Create the release with changes from changelog based on the pushed tag.
-
Merge tag to master.
-
Website
wavebeans.io:- Update documentation
- Update release notes: https://wavebeans.io/wavebeans/release_notes.html
- Update links from
/docs/user/libto/docs/api - Update links from
/docs/user/httpto/docs/http - Update links from
/docs/user/clito/docs/cli - Update links from
/docs/user/exeto/docs/exe .mdto.html
- Update links from
-
Social channels:
- Post the link on twitter and telegram channel.