Hi Aaron, Lazy consensus is the most "proper" way for it and no need for a non-lazy consensus voting [1]. Lazy consensus is simply an announcement of 'silence gives assent' [2]. What this means is that one make a proposal and state that he/she will start implementing it in 72 hours unless someone objects. 72 hours is chosen because it accounts for different timezones and non-apache commitments.
Here is an example: [3]. On the other hand, there is another example of being a volunteer but not starting a lazy consensus voting: [4]. All in all, the more "Apache Way" is to start a Discuss thread about cutting a new release and proposing yourself as a release manager for. Kind Regards, Furkan KAMACI [1] http://www.apache.org/dev/release-publishing.html#release_manager [2] https://community.apache.org/committers/lazyConsensus.html#stating-lazy-consensus [3] https://lists.apache.org/thread.html/r8a8c12bc5d6f89a3e67454277b22875289be8de4799c03e01d2e5b8b%40%3Cdev.beam.apache.org%3E [4] https://lists.apache.org/thread.html/r024754c61d9f663f71b7db52bc9b815c9853e7cc486a8185d670f478%40%3Cdev.druid.apache.org%3E On Fri, Mar 27, 2020 at 10:02 PM Aaron Radzinski <[email protected]> wrote: > Mentors - do we need to have a vote on selecting the Release Manager? We > are getting close to to be ready for our first release under ASF... I would > like to volunteer for this role. > > Thanks, > -- > Aaron Radzinski >
