Unfortunately, the release manager has to be a committer. There are practical reasons (you need write access to several ASF systems) and legal ones (you are making the release on behalf of Apache).
That said, I very much appreciate your offer to help. Could you help with the logistics? For example compiling release notes, running test builds, and chasing up the various JIRA cases and pull requests that are required in the release. The release instructions[1] describe the pre-release checks that need to be performed. If you did those the actual release would run more smoothly. Julian [1] https://calcite.apache.org/docs/howto.html#making-a-release-for-calcite-committers <https://calcite.apache.org/docs/howto.html#making-a-release-for-calcite-committers> > On Aug 23, 2016, at 10:44 AM, Atri Sharma <[email protected]> wrote: > > I can be the release manager (my first time,so would need support and > bootstrapping, but would love to help). > > Regards, > > Atri > > On Tue, Aug 23, 2016 at 11:11 PM, Julian Hyde <[email protected]> wrote: > >> It’s time to start work on Calcite release 1.9, so we can hit the “end of >> August” target. >> >> Does this timeline (end of August) still work for everyone? >> >> Would anyone like to be release manager? >> >> Are there any issues that people would like to get into 1.9 (and are >> prepared to work on)? >> >> It should be quite a straightforward release. I have logged >> https://issues.apache.org/jira/browse/CALCITE-1356 < >> https://issues.apache.org/jira/browse/CALCITE-1356> to track. >> >> Julian >> >> > > > -- > Regards, > > Atri > Apache Concerted
