Laurent,
There are definitely some steps that require privileges, but the management of the process doesn't require privileges. The key steps are a) developing consensus on the content of the release, b) building a release candidate and c) conducting the vote. After these, pushing the artifacts may require some mojo, but it is easy to get somebody to help. None of these other steps require more than a commit bit. Remember that the core point of a release is the community involvement, not the technical aspects of packaging. On 2021/04/12 21:45:22, Laurent Goujon <[email protected]> wrote: > Hi Ted, > > I was led to believe that only a PMC member could perform some of the > release tasks, but if not the case, I'm happy to volunteer for the next > one. Since it would be my first release, is there any document detailing > the list of tasks to be completed? > > On Mon, Apr 12, 2021 at 1:55 PM Ted Dunning <[email protected]> wrote: > > > Hey Ray, > > > > Any Drill committer should be able to act as a release manager. > > > > My guess is that you know several Drill committers at Dremio who might be > > able to help with this. > > > > > > > > On Mon, Apr 12, 2021 at 12:00 PM Ray Lum <[email protected]> wrote: > > > > > Hi Drill community, > > > > > > Is there a process for requesting a release of the latest code currently > > in > > > master? I am keen on adopting some of the changes if they were in an > > > official release. > > > > > > Thanks kindly, > > > Ray > > > > > >
