Please add me as well.

> On 12 May 2020, at 09:51, Sam Tunnicliffe <s...@beobal.com> wrote:
> 
> Me too.
> 
>> On 11 May 2020, at 20:23, Jake Luciani <j...@apache.org> wrote:
>> 
>> Happy to lend a hand
>> 
>> On Mon, May 11, 2020 at 3:12 PM Eric Evans <john.eric.ev...@gmail.com>
>> wrote:
>> 
>>> I can take a turn.
>>> 
>>> On Fri, May 8, 2020 at 11:10 AM Vinay Chella <vinaykumar...@gmail.com>
>>> wrote:
>>>> 
>>>> I would like to help as well.
>>>> 
>>>> 
>>>> On Fri, May 8, 2020 at 8:54 AM Chris Lohfink <clohfin...@gmail.com>
>>> wrote:
>>>> 
>>>>> I'd like to get involved in this as well.
>>>>> 
>>>>> On Thu, May 7, 2020 at 2:06 PM Jon Meredith <jmeredit...@gmail.com>
>>> wrote:
>>>>> 
>>>>>> Sign me up.
>>>>>> 
>>>>>> On Thu, May 7, 2020 at 12:36 PM Robert Stupp <sn...@snazy.de> wrote:
>>>>>>> 
>>>>>>> I can help
>>>>>>> 
>>>>>>> --
>>>>>>> Robert Stupp
>>>>>>> @snazy
>>>>>>> 
>>>>>>>> Am 07.05.2020 um 20:29 schrieb Mick Semb Wever <m...@apache.org>:
>>>>>>>> 
>>>>>>>> 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.
>>>>>>>> 
>>>>>>>> regards,
>>>>>>>> Mick
>>>>>>>> 
>>>>>>>> 
>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>>>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>>>>>> 
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>>>>> 
>>>>>> 
>>>>> 
>>>> --
>>>> 
>>>> Thanks,
>>>> Vinay Chella
>>> 
>>> 
>>> 
>>> --
>>> Eric Evans
>>> john.eric.ev...@gmail.com
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>> 
>>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to