-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Addressing a handful of open github issues (#741)
* Github Issue 718. Add papers to Hector manuscript lists, including V3.2.0 manuscript * github issue 727. rename FCH4 to RF_CH4 to match all other RF output * Add a new release checklist * github issue 734, add output streams * quite build message * github issue 740, add matilda refernces * github issue 735, add ref temperature period to plot
- Loading branch information
Showing
19 changed files
with
175 additions
and
152 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
name: Release | ||
about: Checklist! | ||
--- | ||
|
||
Since the dev branch only includes materials that have been peer-reviewed at least once this PR review process should be relatively smooth should. That being said, before merging this branch into main and the new release is created several things must be completed first. | ||
|
||
* Open a PR into main branch, it should be titled with the new release number | ||
* Let Leeyabot generate a report detailing how the Hector output has changed! | ||
* Add text to the PR documenting the major model changes. The PR is going to serve as an important record | ||
* Pass automated checks | ||
* Change the version number in the DESCRIPTION file | ||
* Update the NEWS.md, are links additional materials necessary? Does the release need a new naming file? | ||
* Check to make sure the internal package data is up to date (fxntable, inputstable, unitstable) | ||
|
||
After merging PR | ||
|
||
* Create the release via zenodo | ||
* Add the zenodo links to README / NEWS & push directly to main | ||
* Create new dev branch & update the DESCRIPTION version number to support the pkgdown documentation for the developmental branch! | ||
* Add archived outputstreams to release assets! | ||
|
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
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
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
Oops, something went wrong.