Skip to content

Conversation

jennyhickson
Copy link
Collaborator

A refresh of the review process documentation including updating the pull request page with details of review states and reviewers, and updating the code review and scitech review guidance to remove references to tickets and templates.

@jennyhickson jennyhickson added the crSet This is added to a pull request once the SSD team have assigned a code reviewer. label Sep 22, 2025
@jennyhickson jennyhickson marked this pull request as draft September 22, 2025 14:04
@jennyhickson jennyhickson marked this pull request as ready for review September 23, 2025 11:44
Copy link
Contributor

@james-bruten-mo james-bruten-mo left a comment

Choose a reason for hiding this comment

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

Nothing particularly controversial I think

are marked on the :ref:`Ticket Summary wiki pages <template>` by those signing
off the approval.
Every pull request will need to get approval from a group of people. These
approvals are marked in the pull request description by those signing off the
Copy link
Contributor

Choose a reason for hiding this comment

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

Github Reviewers?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hmm, realised this page needs going over more generally. And presumeably config owners will still need to be via the trac.log.

Copy link
Contributor

Choose a reason for hiding this comment

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

Not convinced it needs to stay in the trac.log? For UM we'll need a custom action, which can use the code in my open suite_report PR. But for Apps I think we have a normal looking CODEOWNERS file? But sure, we can revisit this section later when things are a touch clearer

.. tip::

From vn13.2 the :ref:`trac.log <traclog>` summary of your testing will also
The :ref:`trac.log <traclog>` summary of your testing will also
Copy link
Contributor

Choose a reason for hiding this comment

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

Github Reviewers?


* Review suggestions and comments are formed into conversations. The `Resolve
Conversation` button is used by the reviewer when they are satisfied to
close that part of the review. The developer should not resolve
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe make the not bold here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

suggestions for other suitable reviewers or you can approach anyone who would
have good insight into the changes made.

Changes that have a linked LFRic Core ticket should find a SciTech reviewer from
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure this line is needed - they don't have to be specifically SR for a linked Apps ticket? There are Apps-Core science tickets that would benefit from an actual science review?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think this came about (the line was pre-existing in the old reviewers file) because they felt that Core tickets needed a CCD reviewer for either science or code review. But perhaps thats just one for us to keep an eye on as assigners

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah I think so - I'm in the habit of doing so

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

jennyhickson and others added 5 commits September 23, 2025 15:24
Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>
Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>
Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>
Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>
@jennyhickson jennyhickson linked an issue Sep 23, 2025 that may be closed by this pull request
Copy link
Contributor

@james-bruten-mo james-bruten-mo left a comment

Choose a reason for hiding this comment

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

Just one small suggestion

Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>
Copy link
Contributor

@james-bruten-mo james-bruten-mo left a comment

Choose a reason for hiding this comment

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

Ta

@james-bruten-mo james-bruten-mo merged commit 9872f94 into MetOffice:github_wps Sep 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crSet This is added to a pull request once the SSD team have assigned a code reviewer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Code Owners
2 participants