Skip to content

Add Maintainer Version Update process description to wiki#2840

Open
KFosterReed wants to merge 12 commits into
devfrom
Maintainer-Version-Update-Process
Open

Add Maintainer Version Update process description to wiki#2840
KFosterReed wants to merge 12 commits into
devfrom
Maintainer-Version-Update-Process

Conversation

@KFosterReed

@KFosterReed KFosterReed commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

Context

Issue(s) closed by this pull request: closes #2796

This PR adds the process developed through discussion in issue #2796 into a wiki page to document the process for reference in the future.

Note that when issue #2818 is complete, the references to the SME Review process on this page should be linked to that page

@github-actions

github-actions Bot commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

Current Coverage: 99%

Mypy errors on Maintainer-Version-Update-Process branch: 1420
Mypy errors on dev branch: 1420
No difference in error counts

@github-actions

github-actions Bot commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

🚨 Please update the changelog. This PR cannot be merged until changelog.md is updated.

@LisaM-kiwi LisaM-kiwi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me!

@github-actions

Copy link
Copy Markdown
Contributor

Current Coverage: 99%

Mypy errors on Maintainer-Version-Update-Process branch: 1191
Mypy errors on dev branch: 1191
No difference in error counts

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

Current Coverage: 99%

Mypy errors on Maintainer-Version-Update-Process branch: 1191
Mypy errors on dev branch: 1191
No difference in error counts

@JoeWaddell JoeWaddell left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great, pending a couple questions! Hits the right amount of detail for me, as it works as a good set of guidelines without being too restrictive.

Also, it now works well with #2813, and I think the code there can link to or otherwise reference this writeup.

Comment thread docs/_src/_wiki/Version-Update-Workflow.rst
Comment thread changelog.md Outdated

After ``test`` is updated
-------------------------
- During the testing phase, SME Maintainers will evaluate integrated model performance. (link to Scientific Evaluation Process).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reminder that link needed here! Or to add the Issue number while it's still in progress

Comment thread docs/_src/_wiki/Version-Update-Workflow.rst
KFosterReed and others added 7 commits May 12, 2026 16:08
Clarified the explanation regarding bug fixes in patch updates.
Create distinct processes for Major, Minor, and Patch updates, including deliverables and review requirements.
Co-authored-by: JoeWaddell <109082924+JoeWaddell@users.noreply.github.com>
Corrected grammatical errors and improved clarity in the version update workflow documentation.
Correct formatting and spelling errors in the version update workflow documentation.
Removed link reference from the evaluation process description.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Develop and Document process for communicating with RuFaS Maintainers during version update process

3 participants