+1 for leesf, driving the release.. >From http://www.apache.org/dev/release-publishing.html#release_manager, it does explicitly confirm that any committer can be RM. I am happy to volunteer my services to assist leesf in the process.
@all : Please speak up if you have concerns with the release/timelines. Side note: There are OPEN jiras here https://issues.apache.org/jira/issues/?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1 , targeted against the release. So if you are interested, please grab them so we can expedite our progress. On Wed, Dec 11, 2019 at 5:27 PM leesf <leesf0...@gmail.com> wrote: > Hi Balaji, > > Thanks for kicking the discussion off. > > +1 to release next version as we made many improvements since last released > version and Jan is reasonable considering the upcoming holidays. > > Besides I am wondering if I can be the release manager of 0.5.1 to work > with you. It is always meaningful to help the community as much as > possible. > > Best, > Leesf > > Balaji Varadarajan <vbal...@apache.org> 于2019年12月12日周四 上午1:08写道： > > > Hello all, > > > > In the spirit of making Apache Hudi (incubating) releases at regular > > cadence, we are starting this thread to kickstart the planning and > > preparatory work for next release (0.5.1). > > > > As discussed in yesterdays meeting, the current plan is to have a release > > by end of Jan 2020. > > > > As described in the release guide (see References), the first step would > be > > identify the release manager for 0.5.1. This is a consensus-based > decision > > of the entire community. The only requirements is that the release > manager > > be Apache Hudi Committer as they have permissions to perform some of the > > release manager's work. The committer would still need to work with PPMC > to > > write to Apache release repositories. > > > > There’s no formal process, no vote requirements, and no timing > requirements > > when identifying release manager. Any objections should be resolved by > > consensus before starting the release. > > > > In general, the community prefers to have a rotating set of 3-5 Release > > Managers. Keeping a small core set of managers allows enough people to > > build expertise in this area and improve processes over time, without > > Release Managers needing to re-learn the processes for each release. That > > said, if you are a committer interested in serving the community in this > > way, please reach out to the community on the dev@ mailing list. > > > > If any Hudi committer is interested in being the next release manager, > > please reply to this email. > > > > References: > > Planned Tickets: Jira Tickets > > < > > > https://jira.apache.org/jira/issues/?jql=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1 > > > > > Release Guide: Release Guide > > < > > > https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+%28incubating%29+-+Release+Guide > > > > > > > Thanks, > > Balaji.V > > (On behalf of Apache Hudi PPMC) > > >
