-
Notifications
You must be signed in to change notification settings - Fork 101
Preparing a Release
Philipp Naderer-Puiu edited this page May 3, 2022
·
8 revisions
- Update the version numbers:
-
gradle.properties
has aversion = MAJOR.MINOR.PATCH
string - modify the version in
src/org/ringojs/engine/RhinoEngine.java
toCollections.unmodifiableList(Arrays.asList(MAJOR, MINOR, PATCH));
-
- Create a new release tag on Github.
- Check the version number with
ringo -v
- Create a clean build without any packages in
packages
. You can usebotic/ringodev-docker
for this task. - Test the build on your local machine
- Sign the checksums. Yo can use
botic/ringodev-tools
for this task. - Upload everything on ringojs.org under
https://github.com/ringo/ringojs.org/tree/master/releases
- Update the change log:
http://ringojs.org/documentation/release_MAJOR_MINOR_PATCH/
- Change the footer and documentation frontpage to the newest release on ringojs.org
- Update the brew formula (with
--dry-run
first):
- Hint: You have to run
hub fork
inside of/usr/local/Homebrew/
before the first run! brew update && brew doctor
brew bump-formula-pr --strict ringojs --url=https://github.com/ringo/ringojs/releases/download/vX.Y.Z/ringojs-X.Y.Z.tar.gz --sha256=a04b....... --dry-run
- Announce the release on the mailing list, Twitter, …