aboutsummaryrefslogtreecommitdiff
path: root/node_modules/highlight.js/docs/release-process.rst
diff options
context:
space:
mode:
Diffstat (limited to 'node_modules/highlight.js/docs/release-process.rst')
-rw-r--r--node_modules/highlight.js/docs/release-process.rst20
1 files changed, 0 insertions, 20 deletions
diff --git a/node_modules/highlight.js/docs/release-process.rst b/node_modules/highlight.js/docs/release-process.rst
deleted file mode 100644
index 11cf28947..000000000
--- a/node_modules/highlight.js/docs/release-process.rst
+++ /dev/null
@@ -1,20 +0,0 @@
-Release process
-===============
-
-Note: this is intended for core committers.
-
-* Update CHANGES.md with everything interesting since the last update.
-
-* Update version numbers using the three-part x.y.z notation everywhere:
-
- * The header in CHANGES.md (this is where the site looks for the latest version number)
- * ``"version"`` attribute in package.json
- * Two places in docs/conf.py (``version`` and ``release``)
-
-* Commit the version changes and tag the commit with the plain version number (no "v." or anything like that)
-
-* Push the commit and the tags to master (``git push && git push --tags``)
-
-Pushing the tag triggers the update process which can be monitored at http://highlightjs.org/api/release/
-
-When something didn't work *and* it's fixable in code (version numbers mismatch, last minute patches, etc), simply make another release incrementing the third (revision) part of the version number.