docs/release-calendar: plan 20.3 release
/cc past maintainers: @dbaker @evelikov @tanty @jasuarez
That said, since @dbaker did the 20.2 release, it shouldn't be him doing the next one (per our docs):
In order to keep the whole releasing team up to date with the tools used, best practices and other details, the member in charge of the next feature release will be in constant rotation.
@evelikov @tanty @jasuarez any takers?
Or is there anyone new interested in putting one a release maintainer's hat?