Update process doc to specify which commit to tag [ci skip] (emscripten-core#11857)

kripken · web-flow · commit 850f87bfbcec · 2020-08-10T17:24:22.000-07:00
diff --git a/docs/process.md b/docs/process.md
@@ -61,12 +61,9 @@ How:
    adding the version and the hash. Updating the "latest" tag there to the new
    release is possible, but can also be deferred if you want to do more testing
    before users fetching "latest" get this release.
-2. Tag the emscripten repo on the emscripten commit used by that release (which
-   you can tell from the DEPS file), using something like
-   `git checkout [COMMIT]` ; `git tag [VERSION]` ; `git push --tags`.
-3. Tag the emsdk repo as well, on the commit that does the update, after it
+2. Tag the emsdk repo as well, on the commit that does the update, after it
    lands on master.
-4. Update
+3. Update
    [emscripten-version.txt](https://github.com/emscripten-core/emscripten/blob/master/emscripten-version.txt)
    in the emscripten repo. This is a delayed update, in that the tag will refer
    to the actual release, but the update to emscripten-version.txt is a new
@@ -77,7 +74,10 @@ How:
      when that's unlikely, etc.
    * There is no need to open a PR for this change, you can optionally just
      commit it directly.
-
+4. Tag the emscripten repo on the emscripten commit on which
+   `emscripten-version.txt` was updated. (This could also be the commit from the
+   DEPS file as well, but this way is less confusing when just working on the
+   emscripten repo, and the difference should only be one commit anyhow.)
 
 Major version update (1.X.Y to 1.(X+1).0)
 -----------------------------------------
