Set version to 2.2.0

[jvegreg]

Just what it says

• ☝ Create an issue to discuss what you are going to do

Checklist

• PR has a descriptive title for the changelog
• Code follows the style guide
• Documentation is available for new functionality
• YAML files pass pre-commit or yamllint checks
• Circle/CI tests pass
• Codacy code quality checks pass
• Documentation builds successfully on readthedocs
• Unit tests are available

If you make backwards incompatible changes to the recipe format:

• Update ESMValTool and link the pull request(s) in the description

---

To help with the number pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[valeriupredoi]

good one @jvegasbsc - we're on the road again 😁 A few things:

• after we merge this, we need the release branch - ask @mattiarighi to set no-push/no-merge permissions on that - or you have these prerogatives already, if you do pls set them on that branch, just you and me can work on it; then we'll ask peeps to run recipes; we should also make sure that you have the pypi and anaconda credentials to upload the packages via automatic Github Actions - maybe we can chat over a call soon about all this jazz?

For here:

• you'll have to change the version in esmvalcore/_version.py and in package/meta.yaml too
• you'll have to change the date-released: 2020-10-12 in CITATION.cff too

🍺

[jvegreg]

Yes, tomorrow morning it's ok? I can not set an hour now, but will contact you in the morning

[valeriupredoi]

sounds good, my morning starts at 11am your time, so no rush 😁 I'll set up a zoom call for us

[jvegreg]

I updated the zenodo link to version 2.1, so at least it does not point to a beta release and set up the release date to next monday. We may need to update it, but its a better approximation just in case we forget.

By the way, I love this unique identifier loop: I need to do the release to get the number but I would like to have the number in the release metadata

[bouweandela]

Did you find the instructions we have available for making a release? They live here: https://docs.esmvaltool.org/projects/esmvalcore/en/latest/contributing.html#how-to-make-a-release

One of the things mentioned there is the list of files in which the version number lives. It looks like you forgot to update package/meta.yaml, could you update the version number in that file too?

[valeriupredoi]

let's have a list of things that we want merged in the release branch before release #982

[valeriupredoi]

this is beautiful: