Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature 2159 release guide #2183

Merged
merged 1 commit into from
May 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 11 additions & 18 deletions docs/Release_Guide/release_steps/common/update_dtc_website.rst
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Update DTC Website
* For *Related Community Code* select both the METplus and the |projectName|
options (For Macs, hold the Command key to select both).

* For *Version Label* type "|projectRepo| X.Y.Z betaN".
* For *Version Label* type "|projectRepo| X.Y.Z-betaN".

* Select the release type (*Recommended* for official or bugfix releases or
*Development* for development versions).
Expand Down Expand Up @@ -48,8 +48,9 @@ Update DTC Website

* Update the existing releases, as needed.

* For a development release, change any previous *Development*
versions to *Other*.
* For a development release, ensure the "Release Type" is set to
*Development* and change any previous *Development* versions to
*Other*.

* For a bugfix or official release, change any previous
*Recommended* versions to *Other*.
Expand All @@ -59,22 +60,14 @@ Update DTC Website

* Create or edit the "Coordinated METplus Version X.Y" software release.

* For a beta1 development release, create the "Coordinated METplus
Version X.Y" release entry if it doesn't already exist. Ensure the
"Release Type" is set to *Development*. Add links for the |projectRepo|
X.Y.Z beta1, the METplus "Documentation", the METplus "Existing Builds
and Docker" page, and the "Release Notes". Add to the Release Notes a link to the
|projectRepo| Release Notes.
* For an official release, create the "Coordinated METplus Version X.Y"
release entry if it doesn't already exist. Ensure the "Release Type"
is set to *Recommended*. Consider changing the "Release Type" of
previous coordinated releases from *Recommended* to *Other*. Add
links for the |projectRepo| X.Y.Z, the METplus "Documentation",
the METplus "Existing Builds and Docker" page, and the "Release Notes".
Make the Release Notes a link to the |projectRepo| Release Notes.

* For a beta2 or beyond development release, update the existing link and text in
the "Coordinated METplus Version X.Y" release section with the updated
development release information.

* For an official release, update the existing link and text in
the "Coordinated METplus Version X.Y" release section with the X.Y.Z
information. Change the "Release Type" from *Development* to
*Recommended*. Consider changing the "Release Type" of previous coordinated releases from *Recommended* to *Other*.

* For a bugfix release, update the existing link and text in
the "Coordinated METplus Version X.Y" release section with the
X.Y.Z+1 information.
Expand Down