ANTS 2.2.0 Release

[arjclark]

ANTS 2.2.0 has now been released.

A major driver for this release is to enable migration of ANTS to GitHub - this is the last release of ANTS on MOSRS. This means many of the changes involve moving science code from core ANTS to Contrib, and removing rose stem source files from the repository. Source files are now stored locally, see the documentation for more information.

Given the nature of these updates, any branches in progress will need to be rebranched from head of trunk. If you need advice, please contact the MIAO inbox: miao@metoffice.gov.uk.

A set of release notes can be found in our documentation.

For a full list of tickets closed against this release, see the release ticket.

There is a parallel 2.2.0 tag of Contrib.

[ScottWales]

Are the source files available to partners?

[arjclark]

Hi Scott, no, not at this time. Everything you need for unittesting should be there for you though - the source files should only be needed for rose-stem - if there's something missing do let us know though.

RE the source files, there are/were IPR concerns with those which mean we can't openly distribute them (along with binary files being in a version control system being a bad idea in the first place so we want all that out of the repo ahead of git migration). ANTS on github will be fully open, not just private to the partnership (contrib will remain partnership only initially though). We've also had no indication any other site was running rose-stem for some time as the rose-stem workflows are only being written/maintained for metoffice infrastructure or only support the "meto" site and when we've asked about other sites using our rose-stems have had nothing back. That in mind, we've worked on the assumption that other sites are not using rose-stem workflows so don't currently have a plan for running things anywhere but the metoffice site.

We currently have plans for re-engineering the rose-stem workflows into a single unified test framework in order to make sure science codes are end-to-end tested as they start getting split across "classic" contrib and UG-contrib implementations. If you'd like that to be something you can run at your site and would be happy to get involved in implementing the site-specific parts, please do ping an email over to miao - we'd love the collaboration!