Maintaining UM Versions

ACCESS-NRI / accessdev-Trac-archive

Archive accessdev Trac contents as issues

Apache License 2.0

0 stars 0 forks source link

Open penguian opened 9 years ago

penguian commented 9 years ago

keyword_TIWG | by saw562@nci.org.au

How do we maintain the UM past the Met Office schedule, e.g. adding bugfixes to old releases

Branches for each version?
- vn10.0_access
- vn10.1_access
Are branches owned by an ACCESS project, or an individual?
What are the working practices for adding patches? Do any changes need to be present in trunk as well?
Do patches need to preserve bit-reproducibility?

Issue migrated from trac:197 at 2024-01-31 18:13:56 +1100

penguian commented 9 years ago

@scott.wales@bom.gov.au commented

Operational vs Research support
- Research less requirements
- Ops need to maintain version in use
Every operational version should have a branch
How is this managed at the Met Office Ops?
- Individual's or shared branches
- Naming conventions
- What happens when someone leaves?
How are revisions for e.g. PS releases managed?

SRS forum 14/8

penguian commented 9 years ago

@scott.wales@bom.gov.au commented

Peter will follow up with Met Office

penguian commented 8 years ago

@scott.wales@bom.gov.au changed priority from major to minor

penguian commented 8 years ago

@scott.wales@bom.gov.au changed status from new to assigned

penguian commented 8 years ago

@scott.wales@bom.gov.au changed owner from ` toaxs599`