Release Manager role, schedule for next releases (#3117)

* Release Manager role, schedule for next releases

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

* Clarified that the release manager should take care of other components

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

* Add tentative dates, removed past releases

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

* Removed objectiser from the schedule

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

GOVERNANCE.md

@@ -35,6 +35,14 @@ mailing list containing the following information:
 
 Two other maintainers need to second the nomination. If no one objects in 5 working days (U.S.), the nomination is accepted.  If anyone objects or wants more information, the maintainers discuss and usually come to a consensus (within the 5 working days). If issues can't be resolved, there's a simple majority vote among current maintainers.
 
+## Maintainer duties
+
+Maintainers are required to participate in the project, by joining discussions, submitting and reviewing pull requests, answering user questions, among others.
+
+Besides that, we have one concrete activity in which maintainers have to engage from time to time: releasing new versions of Jaeger. This process ideally takes only a couple of hours, but requires coordination on different fronts. Even though the process is well documented, it is not without eventual glitches, so, each release needs a "Release Manager". How it works is described in the [RELEASE.md](RELEASE.md) file.
+
+Maintainers are also encouraged to speak about Jaeger at conferences, especially KubeCon+CloudNativeCon which happens twice a year. This event has a "maintainer track", in which maintainers can give an introduction and/or a deep dive about their projects. The Jaeger project has always participated since it became part of the CNCF.
+
 ## Changes in Maintainership
 
 We do not expect anyone to make a permanent commitment to be a Jaeger maintainer forever. After all, circumstances change,

RELEASE.md

@@ -25,3 +25,20 @@
 6. Announce the release on the [mailing list](https://groups.google.com/g/jaeger-tracing), [slack](https://cloud-native.slack.com/archives/CGG7NFUJ3), and [twitter](https://twitter.com/JaegerTracing?lang=en).
 
 Maintenance branches should follow naming convention: `release-major.minor` (e.g.`release-1.8`).
+
+## Release managers
+
+A Release Manager is the person responsible for ensuring that a new version of Jaeger is released. This person will coordinate the required changes, including to the related components such as UI, IDL, and jaeger-lib and will address any problems that might happen during the release, making sure that the documentation above is correct.
+
+In order to ensure that knowledge about releasing Jaeger is spread among maintainers, we rotate the role of Release Manager among maintainers.
+
+Here are the release managers for future versions with the tentative release dates. The release dates are the first Wednesday of the month, and we might skip a release if not enough changes happened since the previous release. In such case, the next tentative release date is the first Wednesday of the subsequent month.
+
+| Version   | Release Manager  | Tentative release date |
+|-----------|------------------|------------------------|
+| 1.24.0    | @pavolloffay     |  7 July      2021      |
+| 1.25.0    | @vprithvi        |  4 August    2021      |
+| 1.26.0    | @yurishkuro      |  1 September 2021      |
+| 1.27.0    | @joe-elliott     |  6 October   2021      |
+| 1.28.0    | @albertteoh      |  3 November  2021      |
+| 1.29.0    | @jpkrohling      |  1 December  2021      |