I volunteer to do 1.24. There’s one part of the release process that only a PMC member can do - namely, to sign the artifacts. But that’s only a small part of the process, and you can easily get a PMC member to do it for you. A much larger part of the process is the herding of cats (committers, bugs, pull requests, release notes). So, yes, a committer can definitely be a release manager.
How does the PMC decide which committers to promote to PMC members? We are looking for people who help out around the project, going above and beyond the basic needs of each task to make the project a better place. If you are a committer, helping with the release process is a good way to earn merit. Julian > On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis <[email protected]> wrote: > > Many thanks Haisheng and Danny for stepping up! I added you to the list. > There are two spots left, if nobody else comes up I will take one of them! > > Release Target date Release manager > ======= =========== =============== > 1.19 2019-03 Kevin > 1.20 2019-06 Michael > 1.21 2019-09 Stamatis > ======= =========== =============== > 1.22 2019-12 Andrei > 1.23 2020-02 Haisheng > 1.24 2020-04 Julian > 1.25 2020-06 Danny > 1.26 2020-08 > > > > On Sat, Nov 30, 2019 at 9:52 AM Danny Chan <[email protected]> wrote: > >> BTW, >> I can volunteer to be the release manager for v1.25 or v1.26. >> >> Best, >> Danny Chan >> 在 2019年11月30日 +0800 PM2:13，[email protected]，写道： >>> >>> I can volunteer to be the release manager for v1.23 or v1.24. >>
