From db2327aeab84cd6966d1179b58bfe51ef155af6a Mon Sep 17 00:00:00 2001
From: Christine Kim <125395064+chkim-usgs@users.noreply.github.com>
Date: Tue, 8 Oct 2024 13:58:52 -0400
Subject: [PATCH] Update ISIS release process (#109)
* Update release process for full feature releases
* Changes to updating github docs workflow
* isis demos (#101)
* isis demos
* jquery 3.7.1, del projection demo js, del ext themes
* cleanup unused css and layout
* moved demos, linked in nav
* update links in demos and workshops
* place 4 demos in isis-fundamentals pages, moved workshops
* toc update
---------
Co-authored-by: Jacob Cain <115182890+jrcain-usgs@users.noreply.github.com>
---
.../software-management/public-release-process.md | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/docs/how-to-guides/software-management/public-release-process.md b/docs/how-to-guides/software-management/public-release-process.md
index d728fa1..46db887 100644
--- a/docs/how-to-guides/software-management/public-release-process.md
+++ b/docs/how-to-guides/software-management/public-release-process.md
@@ -22,7 +22,11 @@ In this step, we check the currently failing tests. This is currently a judgemen
### Step 2: Update the GitHub documents
-In this step, we will update the documents that are stored in the GitHub repository. Our changes will be going into the dev branch, so create a fresh local branch off of the dev branch.
+In this step, we will update the documents that are stored in the GitHub repository. There will either be one or two PRs as a result of this step depending on:
+- **One PR**: If there is not an existing branch for this release version as stated in [Step 3, Part A](#part-a-setup-repository), *one* PR for updating the documents is needed because that PR is merged into `dev` then the new release branch is cut from `dev`. Since our changes will be going into the `dev` branch, create a fresh local branch off of `dev`.
+- **Two PRs**: If there is an existing branch for this release version, one PR is needed to go into `dev`. Identical changes should be added to the PR in [Step 3, Part D](#part-d-create-a-pull-request).
+
+The update docs PR into `dev` should be merged *after* the release is officially out and at the end of the public release process to ensure the new ISIS docs endpoint is live and working.
#### Part A: Collecting the Changes in the Release
@@ -428,7 +432,10 @@ There are some important considerations to keep in mind when using this release
* Your e-mail can simply be a link to the external announcement.
-### Step 12: Update the Release Schedule
+### Step 12: Publish Record to DOI
+Referring to [Part F](#part-f-create-a-doi-for-the-release), make sure to check that the code.usgs.gov link for the release is live and publish the record on DOI.
+
+### Step 13: Update the Release Schedule
Update the [release schedule](https://github.com/DOI-USGS/ISIS3/wiki/Release-Schedule) with the date of the release and update any future releases with the appropriate dates. Releases should be nominally 3 months apart.
--
GitLab