Yes, the RM needs to be a committer. And in fact it is easier if they are a PMC member.
But you can definitely help. You could manually run some tests: run the test suite against one of our supported back-end databases, e.g. Elasticsearch or MySQL or MongoDB, and log bugs. Build and run tests on Windows (our coverage there is poor). Also look through the bugs that have been fixed this release [1] and see whether they are adequately tested and documented. And, then there is a release candidate, try building it, and vote in the release thread. Your vote isn’t binding, but still matters. Julian [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20fixVersion%20%3D%201.14.0 <https://issues.apache.org/jira/issues/?jql=project%20=%20CALCITE%20AND%20fixVersion%20=%201.14.0> > On Aug 28, 2017, at 11:22 AM, Jesus Camacho Rodriguez <[email protected]> > wrote: > > I agree that we should create a new release soon to continue > with our normal release cadence. > > I would like CALCITE-1947 to go in before the release, I should > push it this week. > > @Michael, AFAIK you need to be a committer to be the RM. > > -Jesús > > > > On 8/25/17, 6:27 PM, "LogSplitter" <[email protected]> wrote: > >> Hi, >> >> Do you have to be a committer to be release manager. >> >> Whats involved. I will volunteer anyway :-) >> >> Michael. >> >> >> On 08/25/2017 04:07 PM, Julian Hyde wrote: >>> It's about time we did a release. 1.13 was exactly 2 months ago. >>> >>> Does anyone have any constraints on the release date? (Must be before >>> X, must be after Y?) >>> >>> Any volunteers to be release manager? >>> >>> Julian >>> >>> >>> On Fri, Aug 25, 2017 at 3:07 PM, LogSplitter <[email protected]> >>> wrote: >>>> Hello, >>>> >>>> I was wondering if there is any estimated of when calcite 1.14 might be >>>> released. >>>> >>>> I am tossing up whether I use a patched version 1.13 release or wait a >>>> little longer for real 1.14 for work I am needing to ship? >>>> >>>> thanks >>>> Michael >> >
