Methodology for future updating the specialization repos

davidhassell commented 5 years ago

All changes to the specializations will be in the form of Pull Requests (not Issues nor direct commits to the master branch)
Pull requests can be made at any time, but they will not be merged until a public release of the specializations for all 9 realms is due (every ~6 months).
After a merge, all repositories will tagged with the same version
When a public release is due, the Pull Requests will be merged into the master branch, ready to be used by downstream tools (such as the spreadsheet generator).
[x] This methodology will be written up in a CONTRIBUTING.md file in each specialization repository
[x] Tag all specialization repos in their current version with 1
[x] Decide on how formally we want to do a community review of changes - Moved to #69

davidhassell commented 5 years ago

Note that pull requests can be modified in your local branch, so it it most likely that there will be at most one PR per realm for pending for the next release.

davidhassell commented 5 years ago

See https://github.com/ES-DOC/cmip6-specializations-ocean/blob/master/CONTRIBUTING.md

davidhassell commented 5 years ago

CONTRIBUTING.md file now exists in each specialization repository.

davidhassell commented 5 years ago

@momipsl Do you have a preference on tag names for the bundle: v1.0 or 1.0 or ...

davidhassell commented 5 years ago

Settled on v1.0

ES-DOC / esdoc-project

Methodology for future updating the specialization repos #65