Also, the pending release blockers are tagged here, with assignees.

https://github.com/apache/hudi/labels/release-blockers



On Tue, Mar 16, 2021 at 7:49 PM Danny Chan <danny0...@apache.org> wrote:

> Yeah, a separate PR is more reasonable and that is what i'm doing now,
> thanks for the feedback.
>
> Best,
> Danny
>
> Vinoth Chandar <vin...@apache.org> 于2021年3月16日周二 下午11:02写道:
>
> > Hi Danny,
> >
> > We can start with the PR you currently have and iterate on the redesign
> in
> > a separate PR?
> > That way we don't hold up the release due to large site redesign.
> >
> > Thanks
> > Vinoth
> >
> > On Mon, Mar 15, 2021 at 8:03 PM Danny Chan <danny0...@apache.org> wrote:
> >
> > > The 20th seems more reasonable, i'm preparing for the Flink HUDI
> document
> > > (including the quick start) now, i got the impression that the
> community
> > > want to reorganize the web using tabs to separate the Spark, Hive,
> Flink
> > > docs, should i do that in my Flink doc PR ?
> > >
> > > Best,
> > > Danny Chan
> > >
> > > Gary Li <yanjia.gary...@gmail.com> 于2021年3月14日周日 下午12:34写道:
> > >
> > > > Thanks for letting me know vinoth. Ok, will move the targeting date
> to
> > > > 20th.
> > > >
> > > > On Sat, Mar 13, 2021 at 11:23 PM Vinoth Chandar <vin...@apache.org>
> > > wrote:
> > > >
> > > > > Can we make a hard cut off as the 20th? We still have not landed
> the
> > > > multi
> > > > > writer support. Also love to land as many of the larger bug fixes
> as
> > > > > possible.
> > > > >
> > > > > Thanks
> > > > > Vinoth
> > > > >
> > > > > On Sat, Mar 13, 2021 at 4:32 AM Gary Li <yanjia.gary...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > Hi Everyone,
> > > > > >
> > > > > > In order to make this release happen, we need to freeze the
> > codebase
> > > > > soon.
> > > > > > If there are any PRs you would like to add to the release, please
> > > add a
> > > > > > Github release blocker tag or tag me @garyli1019 to do this. The
> > > > > targeting
> > > > > > date for the codebase freeze is Match 15th PST.
> > > > > >
> > > > > > Thanks,
> > > > > > Gary Li
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to