Thanks everyone! I've created a confluence page for the onboarding process. https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Managers+Onboarding
There's some prerequisites there for people to read and follow up on in their own time. Provide feedback and ask questions as needed. On Tue, 12 May 2020 at 14:10, Aleksey Yeshchenko <[email protected]> wrote: > > Please add me as well. > > > On 12 May 2020, at 09:51, Sam Tunnicliffe <[email protected]> wrote: > > > > Me too. > > > >> On 11 May 2020, at 20:23, Jake Luciani <[email protected]> wrote: > >> > >> Happy to lend a hand > >> > >> On Mon, May 11, 2020 at 3:12 PM Eric Evans <[email protected]> > >> wrote: > >> > >>> I can take a turn. > >>> > >>> On Fri, May 8, 2020 at 11:10 AM Vinay Chella <[email protected]> > >>> wrote: > >>>> > >>>> I would like to help as well. > >>>> > >>>> > >>>> On Fri, May 8, 2020 at 8:54 AM Chris Lohfink <[email protected]> > >>> wrote: > >>>> > >>>>> I'd like to get involved in this as well. > >>>>> > >>>>> On Thu, May 7, 2020 at 2:06 PM Jon Meredith <[email protected]> > >>> wrote: > >>>>> > >>>>>> Sign me up. > >>>>>> > >>>>>> On Thu, May 7, 2020 at 12:36 PM Robert Stupp <[email protected]> wrote: > >>>>>>> > >>>>>>> I can help > >>>>>>> > >>>>>>> -- > >>>>>>> Robert Stupp > >>>>>>> @snazy > >>>>>>> > >>>>>>>> Am 07.05.2020 um 20:29 schrieb Mick Semb Wever <[email protected]>: > >>>>>>>> > >>>>>>>> The Cassandra release process has had some improvements to > >>> better in > >>>>>>>> line with the ASF guidelines: sha256 & sha512 checksums, staged > >>>>>>>> artefacts in svnpubsub, dep and rpm repositories complete and > >>> signed > >>>>>>>> in staging, and separate scripts and manual steps merged > >>> together. > >>>>>>>> > >>>>>>>> The updated documentation for cutting, voting, and publishing a > >>>>>>>> release is found here: > >>>>>>>> > >>>>>> > >>> https://cassandra.apache.org/doc/latest/development/release_process.html > >>>>>>>> > >>>>>>>> I am hoping to get as many Committers* and PMC members > >>> interested as > >>>>>>>> possible for cutting a future release. > >>>>>>>> > >>>>>>>> Who is interested? How many names can I get :-) > >>>>>>>> > >>>>>>>> The more that are interested then the easier it is to take turns > >>> and > >>>>>>>> be flexible depending on our own availability each time. I will > >>> help > >>>>>>>> out everyone on their first run. Indeed most of my motivation in > >>>>>>>> getting involved with the release process was to make it all as > >>>>> simple > >>>>>>>> and as forgettable as possible, so the role of the role manager > >>> can > >>>>>>>> change easily from release to release. > >>>>>>>> > >>>>>>>> *When a Committer cuts a release, a PMC member has to perform the > >>>>> very > >>>>>>>> last post-vote publish step. > >>>>>>>> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
