Closed gold2718 closed 8 months ago
I agree, couldnt we have the same readme in all branches? Or at least an updated one in the master? It would be nice to know where to see the 2.1 and 2.3 code for instance. Which requires to know tags and where they sit on branches. Also - couldnt we have the component tags specifically spelled out for a certain release in the release note? Its a bit tedious to seach in Externals.cfg for the tags. Once you have checked out the right NorESM tag to find the right Externals.cfg...
I agree we should update the README.md file on the master
branch, and aim to keep this updated at all time. For long-lived branches, e.g. the noresm2
branch, it can be useful to have a README.md file that provide information about the specific branch, and point to the relevant documentation. Not sure what the best approach would be for development branches, but perhaps best to minimize changes that will cause merge conflicts down the line.
I think it could be useful with a tag list for each release where we highlight (e.g. bold font) component changes from the previous release. This should be straight forward to produce when the release increments the last version digit, but perhaps not so clear for other tags (e.g. noresm2.2
does not follow chronologically from noresm2.1
).
I have updated the releases release-noresm2.1.1, release-noresm2.0.7 and release-noresm2.0.6 with tables for component tags.
I have set the path for the documentation in the right hand side "About" to https://noresm-docs.readthedocs.io/en/latest/ (was previously pointing to noresm2 documentation). The "latest" page just gives an overview of available NorESM versions, and links to the relevant documentation.
The README.md file on the master branch is out of date.
release-noresm2.0.6
andrelease-noresm2.1.1
)?