+1 on vinoyang as the release manager +1 on making a shorter 0.5.2 release.
On 2020/02/19 00:55:34, leesf <[email protected]> wrote: > +1 on vino to be RM, and will help him to release as I can. > > nishith agarwal <[email protected]> 于2020年2月19日周三 上午7:28写道： > > > +1 on minor release focussing on Apache compliance. > > +1 on Vino yang to be Release Manager. > > > > -Nishith > > > > On Tue, Feb 18, 2020 at 11:53 AM [email protected] <[email protected]> > > wrote: > > > > > > > > +1 on minor release focussing on Apache compliance. > > > +1 on Vino yang to be Release Manager. > > > The compliance issues reported on build process in > > > > > https://lists.apache.org/[email protected]:lte=1M:Hudi > > should > > > also be looked upon and be on the jira list (if not already). > > > Thanks,Balaji.V On Tuesday, February 18, 2020, 11:11:49 AM PST, Vinoth > > > Chandar <[email protected]> wrote: > > > > > > +1 on vinoyang as the release manager > > > > > > +1 on making a shorter 0.5.2 release. My only suggestion is to have a > > > concrete focus for this release as "ensuring the hudi release is apache > > > compliant fully" (so it will count towards graduation). > > > > > > if you all agree: top of my mind, we need to probably do/double-check the > > > following. > > > > > > - DISCLAIMER-WIP : We still have a WIP disclaimer, this probably excuses > > > some > > > - be fully compliant with the project maturity model > > > > > > > > https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix > > > , tick of the remaining items here. > > > - Fix the NOTICE issue > > > - Confirm with someone (mentors or incubator or asf docs) on what more > > > needs to be done, to be ASF compliant.. > > > - We could also start tagging JIRAs with 0.5.2, with the above focus. > > > > > > > > > > > > > > > > > > On Tue, Feb 18, 2020 at 5:23 AM vino yang <[email protected]> wrote: > > > > > > > Hi Leesf, > > > > > > > > Thanks for kicking the discussion off. > > > > > > > > +1 for planning to release Hudi 0.5.2. > > > > > > > > The 0.5.2 version is a minor version before 0.6 version, more quickly > > > > release can solve some small problems. > > > > > > > > After releasing Hudi 0.5.1 version, we also fixed some bugs and > > developed > > > > some features. So it is very suitable. > > > > > > > > I am volunteering as a release manager for Hudi 0.5.2. > > > > > > > > WDYT? > > > > > > > > Best, > > > > Vino > > > > > > > > leesf <[email protected]> 于2020年2月18日周二 下午7:42写道： > > > > > > > > > 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.2). > > > > > > > > > > As 0.5.2 is a minor release version and contains some features, bug > > > > fixes, > > > > > code cleanup and some apache compliance issues, and some of them > > > > > have been completed. So I would like to propose the next release date > > > by > > > > > the end of this month(2.29). What do you think? > > > > > > > > > > As described in the release guide (see References), the first step > > > would > > > > be > > > > > identify the release manager for 0.5.2. 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. > > > > > < > > > > > > > > > > > > > > https://jira.apache.org/jira/issues/?jql=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1 > > > > > > > > > > > 2> > > > > > Release Guide: Release Guide > > > > > < > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+%28incubating%29+-+Release+Guide > > > > > > > > > > > > > > > > Thanks, > > > > > Leesf > > > > > (On behalf of Apache Hudi PPMC) > > > > > > > > > > > >
