Opened 4 years ago

Last modified 4 years ago

#197 assigned

Maintaining UM Versions

Reported by: Scott Wales Owned by: Asri Sulaiman
Priority: minor Component: ACCESS model
Keywords: TIWG Cc:

Description

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?

Change History (3)

comment:1 Changed 4 years ago by Scott Wales

  • 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

comment:2 Changed 4 years ago by Scott Wales

Peter will follow up with Met Office

comment:3 Changed 4 years ago by Scott Wales

Owner: set to Asri Sulaiman
Priority: majorminor
Status: newassigned
Note: See TracTickets for help on using tickets.