Clarify release docs slightly (jaegertracing#5809)

Just improving the docs a bit to make sure the release manager does the Jaeger UI before the rest of the directions. Signed-off-by: Jonah Kowall <[email protected]> Signed-off-by: Jared Tan <[email protected]>
JaredTan95 · Aug 28, 2024 · 3fe6cb0 · 3fe6cb0
1 parent 05cb2b3
commit 3fe6cb0
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/RELEASE.md b/RELEASE.md
@@ -5,7 +5,8 @@
     * A curated list of notable changes and links to PRs. Do not simply dump git log, select the changes that affect the users.
       To obtain the list of all changes run `make changelog` or use `scripts/release-notes.py`.
     * The section can be split into sub-section if necessary, e.g. UI Changes, Backend Changes, Bug Fixes, etc.
-    * If the jaeger-ui submodule has changes cut a new release and also upgrade the submodule versions then commit, for example:
+    * If the jaeger-ui submodule has changes cut a new release
+    * Then upgrade the submodule versions and finally commit. For example:
         ```
         git submodule init
         git submodule update