Prepare for 1.7.14 release

README.md

@@ -22,13 +22,16 @@ Rhino is licensed under the [MPL 2.0](./LICENSE.txt).
 <tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_11_Release">Rhino 1.7.11</a></td><td>May 30, 2019</td></tr>
 <tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_12_Release">Rhino 1.7.12</a></td><td>January 13, 2020</td></tr>
 <tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_13_Release">Rhino 1.7.13</a></td><td>September 2, 2020</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_14_Release">Rhino 1.7.14</a></td><td>January 6, 2022</td></tr>
 </table>
 
 [Release Notes](./RELEASE-NOTES.md) for recent releases.
 
 [Compatibility table](https://mozilla.github.io/rhino/compat/engines.html) which shows which advanced JavaScript
 features from ES6, and ES2016+ are implemented in Rhino.
 
+[![GitHub Action Status](https://github.com/mozilla/rhino/actions/workflows/gradle.yml/badge.svg)](https://github.com/mozilla/rhino/actions/workflows/gradle.yml)
+
 [![Mozilla](https://circleci.com/gh/mozilla/rhino.svg?style=shield)](https://app.circleci.com/pipelines/github/mozilla/rhino)
 
 ## Documentation

RELEASE-NOTES.md

@@ -1,5 +1,5 @@
-# Rhino 1.7.14 RC 1
-## November 1, 2021
+# Rhino 1.7.14
+## January 6, 2022
 
 # Highlights
 ## Features
@@ -73,7 +73,7 @@
 
 ## Thanks!
 
-This release contains more than 300 commits from 21 contributors. Thanks to everyone who helped!
+This release contains more than 350 commits from 23 contributors. Thanks to everyone who helped!
 
 # Rhino 1.7.13
 ## September 2, 2020

RELEASE-STEPS.md

@@ -0,0 +1,76 @@
+# Rhino Release Process
+
+## Prepare the repository
+
+Update the version in gradle.properties to the new release version.
+
+Update RELEASE_NOTES.md to include at least a summary of the major features
+of the release. (This is historical, but many find it helpful to have a single
+file in the repo that lists the major changes.)
+
+Update README.md to add a row to the table of releases that points to the
+GitHub release that we'll create in the next step (just follow the pattern
+that's there).
+
+Now might be a good time to run "./gradlew publishToMavenLocal" and use the
+published JARs as a sanity check.
+
+## Update Compatibility Table
+
+The offial Kangax "compat table" now supports Rhino, but it's convenient
+to have our own that shows progress across all releases. Here's how to
+update it:
+
+    git clone -b gh-pages https://github.com/gbrail/node-compat-table.git
+    cd node-compat-table
+
+Now, edit "rhinoall.sh" to include the new release -- it includes a series
+of lines that fetch old releases, and use your local build of the new one.
+Then, update the table:
+
+    ./rhinoall.sh
+
+The resulting "index.html" can be copied into "docs/compat/engines.html" in 
+this repo.
+
+## Push the Release to GitHub
+
+At this point, the current contents of your directory correspond to the 
+new release. Prepare a pull request containing the changes, submit it,
+and merge it -- the result will be that the head of the "master" branch
+will build your new release.
+
+Update to that branch and create a tag for the release, where XX is a number
+like "1_7_14":
+
+    git pull origin master
+    git tag Rhino_XX_Release
+    git push origin Rhino_XX_Release
+
+Now, on the Rhino "Releases" tab in GitHub, create a release that corresponds
+to the new tag. Include the following:
+
+* A cut and paste of the part of RELEASE_NOTES.md added for the release
+* The three JARs created by "./gradlew.jar"
+* The ZIP file created by "./gradlew distZip"
+* A ZIP of the source will be included automatically by GitHub
+
+## Push the release to Maven Central
+
+The "Publish to Maven Central" action on GitHub Actions will automatically
+build the release, sign the JARs, and push it to oss.sonatype.org in the
+"org.mozilla" area. Log in to oss.sonatype.org, verify that all the checks
+that happen there were successful, and "close" the release. It will appear
+on Maven Central a few hours later.
+
+## Update Homebrew
+
+The Homebrew team for Mac does not necessarily pick up Rhino releases 
+automatically. It may be necessary to submit a PR to the "homebrew/homebrew"
+repo in GitHub for a change to the file "Library/Formula/rhino.rb".
+
+## Prepare for Next Release
+
+Now it's time to move to the next "SNAPSHOT" release. Update gradle.properties,
+create a PR, and push the new PR. Now development can proceeed anew!
+