Skip to content

Commit

Permalink
update instructions to find issues for a bugfix release (#1790)
Browse files Browse the repository at this point in the history
  • Loading branch information
georgemccabe authored Sep 19, 2022
1 parent 1fe92cc commit 08263d6
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 2 deletions.
Original file line number Diff line number Diff line change
@@ -1,10 +1,12 @@
Update DTC Website
------------------

* Navigate to https://dtcenter.org and sign in to the Drupal interface.

* Navigate to the downloads page for the |projectRepo| repository at
https://dtcenter.org/community-code/metplus/download

* Sign in to the Drupal interface and edit the Downloads page.
* Click on the Edit button to edit the Downloads page.

* Create a new *Software Release* for the newly released version by clicking
on *Add New Release*.
Expand Down
14 changes: 13 additions & 1 deletion docs/Release_Guide/release_steps/update_release_notes_bugfix.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ release. Open the following URL in a browser:
https://github.com/orgs/dtcenter/projects?type=beta
* Click on the project that corresponds to support for the release, i.e.
|projectRepo| Version X.Y Support
METplus Version X.Y Support

* Navigate to the "Closed Issues" tab.
**If this tab does not exist**, follow these instructions to create it:
Expand All @@ -22,6 +22,18 @@ release. Open the following URL in a browser:
* Enter the following info into the filter bar: **is:closed is:issue**
* Click on the down arrow next to the view and click "Save changes"

* Find the closed issues with dtcenter/|projectRepo| in the Repository column
that have been added since the last bugfix release for |projectRepo|.

* Open the following URL in a browser:

.. parsed-literal::
https://github.com/dtcenter/|projectRepo|/issues
* Navigate to the |projectRepo| X.Y.Z Milestone to check for any issues
that may not appear in the METplus Version X.Y Support project board.

* Update the release-notes.rst file found in the User's Guide directory.

* Consider organizing release notes into logical groups
Expand Down

0 comments on commit 08263d6

Please sign in to comment.