Hi Sina, The release process is documented here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
Some of the logistical bits require the ability to cut branches, create tags and push on the ASF remote (as svn commits), this can be only done by at least a committer [1] who has the minimum privilege to perform these operations; and can get a PMC member to do some of the tasks. My understanding is, that any committer can be a release manager and: * have built support with the dev community (proposed themselve as RM and had no objections at least; and proposed a timeline) * are able to triage and work with Github (committer/PMC have 2FA enabled and added to asf org https://gitbox.apache.org<https://gitbox.apache.org/>, or at least have the triaging role enabled) * have built some support with a PMC member to (a) add their GPG keys, (b) have the PMC member move the src/artifacts post a release vote is passed using subversion * have reputation/access to various tightly-controlled project portals (such as docs/readthedocs, publishing on website, publish community packages i.e. access on download.cloudstack.org) * have the motivation, time/bandwidth, and patience to do this (esp when there are blockers/critical issues and requirements to cut multiple RCs) [1] https://cloudstack.apache.org/who.html Regards. ________________________________ From: Sina Kashipazha Sent: Wednesday, September 21, 2022 03:11 To: us...@cloudstack.apache.org; daan.hoogl...@gmail.com Cc: dev Subject: Re: [DISCUSS] release and release manager 4.18 Sorry to interrupt. I'm curious to know how is the release procedure. Is it possible for me to help or should I be a PMC member? ------- Original Message ------- On Tuesday, September 20th, 2022 at 4:52 PM, Simon Weller <swel...@ena.com.INVALID> wrote: > > > +1 to Daan :-) > ________________________________ > From: Rohit Yadav rohit.ya...@shapeblue.com > > Sent: Tuesday, September 20, 2022 9:43 AM > To: us...@cloudstack.apache.org us...@cloudstack.apache.org; dev > dev@cloudstack.apache.org > > Subject: Re: [DISCUSS] release and release manager 4.18 > > EXTERNAL EMAIL: This message originated outside of ENA. Use caution when > clicking links, opening attachments, or complying with requests. Click the > "Phish Alert Report" button above the email, or contact MIS, regarding any > suspicious message. > > > > +1 thanks for volunteering as 4.18 RM Daan. > > Regards. > > Regards. > ________________________________ > From: Daan Hoogland daan.hoogl...@gmail.com > > Sent: Tuesday, September 20, 2022 7:53:53 PM > To: dev dev@cloudstack.apache.org; users us...@cloudstack.apache.org > > Subject: [DISCUSS] release and release manager 4.18 > > Hello everybody, > As Abhishek is wrapping up the 4.17.1 release. I´d like to start the > discussion about 4.18. Nobody has volunteered as the next release manager > yet and I'd like to give the community the opportunity to prevent it > becoming me. My idea is that we will have set a feature freeze date and > then a target date for the first RC. Iḿ not proposing one now as mine would > probably be too tight a deadline for new features and there are some big > ones out there that we'd want in. > Please let us all know what you have in the pipeline and what you want in > and what time you need, so we can discuss if it is feasible for 4.18. > Also please come forward if you want this task of triaging issues and PRs > and tagging them to go in the release. > thanks > > -- > Daan >
