-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feature 673 metviewer release (#910)
Co-authored-by: jprestop <jpresto@ucar.edu> Co-authored-by: bikegeek <minnawin@ucar.edu>
- Loading branch information
1 parent
a38fca5
commit cabcee6
Showing
9 changed files
with
92 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 changes: 3 additions & 0 deletions
3
docs/Release_Guide/release_steps/metviewer/create_release_extra.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
* If this is a development release, check the box that says "This is a pre-release" | ||
|
||
* Click on "Publish release". |
5 changes: 5 additions & 0 deletions
5
docs/Release_Guide/release_steps/metviewer/update_dtc_website.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
.. include:: release_steps/common/update_dtc_website.rst | ||
|
||
.. |projectName| replace:: |projectRepo| | ||
|
||
.. |addTarfileStep| replace:: Link text should be the name of the release and the URL should be the release page that was just created under the GitHub Releases tab. |
10 changes: 10 additions & 0 deletions
10
docs/Release_Guide/release_steps/metviewer/update_version.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
Update Version Number for Release | ||
--------------------------------- | ||
|
||
Create the version number | ||
|
||
- In the METviewer/docs/version file, assign the version to the '__version__' keyword | ||
- In the METviewer/build.xml file, assign the version in the 'dist' target | ||
- In the METviewer/vebapp/metviewer/metviewer1.jsp file, assign the version to <div id='release'> and <title> | ||
- We are naming releases with X.Y.Z format even if Z is 0. | ||
- In the develop branch, the version should match the upcoming release like X.Y.Z-betaN |
12 changes: 12 additions & 0 deletions
12
docs/Release_Guide/release_steps/metviewer/update_version_bugfix.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
Update Version Number for Release | ||
--------------------------------- | ||
|
||
Update the version number for the bugfix release: | ||
|
||
* For METviewer, the file containing the version number is located at docs/version. | ||
* If the current release is listed as X.Y.Z (major.minor.micro), the bugfix version should be X.Y.Z+1 | ||
(i.e. increment the micro value by 1: 1.1.0 becomes 1.1.1) | ||
* In the METviewer/build.xml file, assign the version in the 'dist' target | ||
* In the METviewer/vebapp/metviewer/metviewer1.jsp file, assign the version to <div id='release'> and <title> | ||
|
||
|
11 changes: 11 additions & 0 deletions
11
docs/Release_Guide/release_steps/metviewer/update_version_official.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
Update Version Number for Release | ||
--------------------------------- | ||
|
||
Remove **-dev** from the version number: | ||
|
||
* We are naming releases with X.Y.Z format even if Z is 0. | ||
* The file containing the version number is located at docs/version. | ||
* In the METviewer/build.xml file, assign the version in the 'dist' target | ||
* In the METviewer/vebapp/metviewer/metviewer1.jsp file, assign the version to <div id='release'> and <title> | ||
|
||
* Save and close the file. |
20 changes: 20 additions & 0 deletions
20
docs/Release_Guide/release_steps/metviewer/update_version_on_develop.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
Update Version on Develop Branch | ||
-------------------------------- | ||
|
||
Change METviewer/docs/version __version__ value to the next release after this one with -dev added | ||
to the end. Releases will loosely following these names, but are subject to | ||
change: | ||
|
||
+-------------------+-----------------------+ | ||
| Release Version | New Develop Version | | ||
+===================+=======================+ | ||
| X.Y.Z-beta1 | X.Y.Z-beta2-dev | | ||
+-------------------+-----------------------+ | ||
| X.Y.Z-beta2 | X.Y.Z-beta3-dev | | ||
+-------------------+-----------------------+ | ||
| X.Y.Z-beta3 | X.Y.Z-rc1-dev | | ||
+-------------------+-----------------------+ | ||
| X.Y.Z-rc1 | X.Y.Z-dev | | ||
+-------------------+-----------------------+ | ||
| X.Y.Z | (X+1).0.0-beta1-dev | | ||
+-------------------+-----------------------+ |