I guess we must do that for current rapid development and iteration. As for the release 0.10.0, after the announcement of only a few days we have received a bunch of bugs reported by the github issues: such as
- the empty meta file: https://github.com/apache/hudi/issues/4249 - and the timeline based marker files: https://github.com/apache/hudi/issues/4230 With the rush in features without enough tests, I'm afraid the major release version is never ready for production, unless there is production validation like in Uber internal. And for minor releases, there should only include the bug fixes, no breaking change, no feature, it should not be a hard work i think. Best, Danny Sivabalan <n.siv...@gmail.com>于2021年12月14日 周二上午4:06写道： > +1 in general. but yeah, not sure if we have resources to do this for every > major release. > > On Mon, Dec 13, 2021 at 10:01 AM Vinoth Chandar <vin...@apache.org> wrote: > > > Hi all, > > > > In the past we had plans for minor releases [1], but invariably we end up > > doing major ones, which also deliver the bug fixes. > > > > The reason was the cost involved in doing a release. We have made some > good > > progress towards regression/integration test, which prompts me to revive > > this. > > > > What does everyone think about a monthly bugfix release on the last > > major/minor version. (not on every major release, we still don't have > > enough contributors to pull that off IMO). So we would be trying to do a > > 0.10.1 early jan for e.g, in this model? > > > > [1] https://cwiki.apache.org/confluence/display/HUDI/Release+Management > > > > Thanks > > Vinoth > > > > > -- > Regards, > -Sivabalan >
