Updated processes for core LFRic developments

[stevemullerworth]

Dear all,

Following the LFRic Repository split we are changing the work instructions for the core LFRic repository to better align with the new LFRic apps repository processes. These processes are, in turn, aligned with the UM development practices so should hopefully be familiar to many LFRic core and LFRic applications developers.

https://code.metoffice.gov.uk/trac/lfric/wiki/LFRicTechnical/DevelopmentProcess

For the LFRic core repository there are now two new page templates for SciTechReview and CodeSysReview. The TicketSummary template has been updated. The questions in each page are broadly aligned with the questions in the equivalent template in the LFRic apps repository.

For those less familiar with UM processes, the SciTech review covers both science and technical issues with a change. As the science apps are no longer included in the core LFRic repository, though, many sci-tech reviews will mainly be technical reviews, covering aspects such as the design of the change. These are aspects that used to be covered by the code review.

The Design Compliance review previously existed as a step in the process for people to request early review of proposed changes that may have implications on the design of the LFRic infrastructure. A design compliance review can now be requested formally in the same way as a sci-tech review. The results of the design review will be recorded in a partially-completed sci-tech review form.

Steve