You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hudi.apache.org by leesf <le...@gmail.com> on 2020/01/08 10:41:38 UTC
[DISCUSS] Code freeze date for next release(0.5.1)
Dear Community,
As discussed before[1], the proposed release date of *end of Jan* for Hudi
0.5.1 is getting closer. And we have many bug fixes and features[2] since
the first release about three months ago.
To make the release version more stable, I would suggest a bug fixing and
testing period of two weeks to be on the safe side. Given the testing
period, I would propose to do the code freeze on the 15th of Jan 23:59 PST
in order to keep the release date. It means that we would cut the Hudi
0.5.1 release branch on this date and no more feature contributions would
be accepted for this branch. And the uncompleted features would be shipped
with next release.
There are 25 jira issues unfinished[3] yet, and you would still pick up the
issues you are interested, among all issues, the major issues would be
update to spark2.4[4], Replace Databricks spark-avro with native
spark-avro[5] and Migrating to Scala 2.12[6], which are important for
runing Hudi on Google Cloud, and we incline to get them on land.
What do you think about the proposed code freeze date? Glad to hear your
thoughts.
Best,
Leesf
[1]
https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
[2]
https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
[3]
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
[4] https://issues.apache.org/jira/browse/HUDI-12
[5] https://issues.apache.org/jira/browse/HUDI-91
[6] https://issues.apache.org/jira/browse/HUDI-238
Re: [DISCUSS] Code freeze date for next release(0.5.1)
Posted by leesf <le...@gmail.com>.
Thanks all for your participation. there are five +1 and no -1, hence I
assume we have reached a consensus. So I will announce the feature freeze
date on the dev mailing list.
Best,
Leesf
Y Ethan Guo <et...@gmail.com> 于2020年1月9日周四 下午2:09写道：
> +1 on the timeline
>
> On Wed, Jan 8, 2020 at 6:01 PM vino yang <ya...@gmail.com> wrote:
>
> > +1
> >
> > Bhavani Sudha <bh...@gmail.com> 于2020年1月9日周四 上午5:24写道：
> >
> > > +1 great idea.
> > >
> > > On Wed, Jan 8, 2020 at 1:20 PM Shiyan Xu <xu...@gmail.com>
> > > wrote:
> > >
> > > > +1. Good idea for testing phase.
> > > >
> > > > On Wed, 8 Jan 2020, 08:26 Vinoth Chandar, <vi...@apache.org> wrote:
> > > >
> > > > > +1 one More week to land two weeks of testing is a good plan
> > > > >
> > > > > On Wed, Jan 8, 2020 at 2:41 AM leesf <le...@gmail.com> wrote:
> > > > >
> > > > > > Dear Community,
> > > > > >
> > > > > > As discussed before[1], the proposed release date of *end of Jan*
> > for
> > > > > Hudi
> > > > > > 0.5.1 is getting closer. And we have many bug fixes and
> features[2]
> > > > since
> > > > > > the first release about three months ago.
> > > > > >
> > > > > > To make the release version more stable, I would suggest a bug
> > fixing
> > > > and
> > > > > > testing period of two weeks to be on the safe side. Given the
> > testing
> > > > > > period, I would propose to do the code freeze on the 15th of Jan
> > > 23:59
> > > > > PST
> > > > > > in order to keep the release date. It means that we would cut the
> > > Hudi
> > > > > > 0.5.1 release branch on this date and no more feature
> contributions
> > > > would
> > > > > > be accepted for this branch. And the uncompleted features would
> be
> > > > > shipped
> > > > > > with next release.
> > > > > >
> > > > > > There are 25 jira issues unfinished[3] yet, and you would still
> > pick
> > > up
> > > > > the
> > > > > > issues you are interested, among all issues, the major issues
> would
> > > be
> > > > > > update to spark2.4[4], Replace Databricks spark-avro with native
> > > > > > spark-avro[5] and Migrating to Scala 2.12[6], which are important
> > for
> > > > > > runing Hudi on Google Cloud, and we incline to get them on land.
> > > > > >
> > > > > > What do you think about the proposed code freeze date? Glad to
> hear
> > > > your
> > > > > > thoughts.
> > > > > >
> > > > > > Best,
> > > > > > Leesf
> > > > > >
> > > > > > [1]
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
> > > > > > [2]
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
> > > > > > [3]
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
> > > > > > [4] https://issues.apache.org/jira/browse/HUDI-12
> > > > > > [5] https://issues.apache.org/jira/browse/HUDI-91
> > > > > > [6] https://issues.apache.org/jira/browse/HUDI-238
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Code freeze date for next release(0.5.1)
Posted by Y Ethan Guo <et...@gmail.com>.
+1 on the timeline
On Wed, Jan 8, 2020 at 6:01 PM vino yang <ya...@gmail.com> wrote:
> +1
>
> Bhavani Sudha <bh...@gmail.com> 于2020年1月9日周四 上午5:24写道：
>
> > +1 great idea.
> >
> > On Wed, Jan 8, 2020 at 1:20 PM Shiyan Xu <xu...@gmail.com>
> > wrote:
> >
> > > +1. Good idea for testing phase.
> > >
> > > On Wed, 8 Jan 2020, 08:26 Vinoth Chandar, <vi...@apache.org> wrote:
> > >
> > > > +1 one More week to land two weeks of testing is a good plan
> > > >
> > > > On Wed, Jan 8, 2020 at 2:41 AM leesf <le...@gmail.com> wrote:
> > > >
> > > > > Dear Community,
> > > > >
> > > > > As discussed before[1], the proposed release date of *end of Jan*
> for
> > > > Hudi
> > > > > 0.5.1 is getting closer. And we have many bug fixes and features[2]
> > > since
> > > > > the first release about three months ago.
> > > > >
> > > > > To make the release version more stable, I would suggest a bug
> fixing
> > > and
> > > > > testing period of two weeks to be on the safe side. Given the
> testing
> > > > > period, I would propose to do the code freeze on the 15th of Jan
> > 23:59
> > > > PST
> > > > > in order to keep the release date. It means that we would cut the
> > Hudi
> > > > > 0.5.1 release branch on this date and no more feature contributions
> > > would
> > > > > be accepted for this branch. And the uncompleted features would be
> > > > shipped
> > > > > with next release.
> > > > >
> > > > > There are 25 jira issues unfinished[3] yet, and you would still
> pick
> > up
> > > > the
> > > > > issues you are interested, among all issues, the major issues would
> > be
> > > > > update to spark2.4[4], Replace Databricks spark-avro with native
> > > > > spark-avro[5] and Migrating to Scala 2.12[6], which are important
> for
> > > > > runing Hudi on Google Cloud, and we incline to get them on land.
> > > > >
> > > > > What do you think about the proposed code freeze date? Glad to hear
> > > your
> > > > > thoughts.
> > > > >
> > > > > Best,
> > > > > Leesf
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
> > > > > [2]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
> > > > > [3]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
> > > > > [4] https://issues.apache.org/jira/browse/HUDI-12
> > > > > [5] https://issues.apache.org/jira/browse/HUDI-91
> > > > > [6] https://issues.apache.org/jira/browse/HUDI-238
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Code freeze date for next release(0.5.1)
Posted by vino yang <ya...@gmail.com>.
+1
Bhavani Sudha <bh...@gmail.com> 于2020年1月9日周四 上午5:24写道：
> +1 great idea.
>
> On Wed, Jan 8, 2020 at 1:20 PM Shiyan Xu <xu...@gmail.com>
> wrote:
>
> > +1. Good idea for testing phase.
> >
> > On Wed, 8 Jan 2020, 08:26 Vinoth Chandar, <vi...@apache.org> wrote:
> >
> > > +1 one More week to land two weeks of testing is a good plan
> > >
> > > On Wed, Jan 8, 2020 at 2:41 AM leesf <le...@gmail.com> wrote:
> > >
> > > > Dear Community,
> > > >
> > > > As discussed before[1], the proposed release date of *end of Jan* for
> > > Hudi
> > > > 0.5.1 is getting closer. And we have many bug fixes and features[2]
> > since
> > > > the first release about three months ago.
> > > >
> > > > To make the release version more stable, I would suggest a bug fixing
> > and
> > > > testing period of two weeks to be on the safe side. Given the testing
> > > > period, I would propose to do the code freeze on the 15th of Jan
> 23:59
> > > PST
> > > > in order to keep the release date. It means that we would cut the
> Hudi
> > > > 0.5.1 release branch on this date and no more feature contributions
> > would
> > > > be accepted for this branch. And the uncompleted features would be
> > > shipped
> > > > with next release.
> > > >
> > > > There are 25 jira issues unfinished[3] yet, and you would still pick
> up
> > > the
> > > > issues you are interested, among all issues, the major issues would
> be
> > > > update to spark2.4[4], Replace Databricks spark-avro with native
> > > > spark-avro[5] and Migrating to Scala 2.12[6], which are important for
> > > > runing Hudi on Google Cloud, and we incline to get them on land.
> > > >
> > > > What do you think about the proposed code freeze date? Glad to hear
> > your
> > > > thoughts.
> > > >
> > > > Best,
> > > > Leesf
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
> > > > [2]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
> > > > [3]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
> > > > [4] https://issues.apache.org/jira/browse/HUDI-12
> > > > [5] https://issues.apache.org/jira/browse/HUDI-91
> > > > [6] https://issues.apache.org/jira/browse/HUDI-238
> > > >
> > >
> >
>
Re: [DISCUSS] Code freeze date for next release(0.5.1)
Posted by Bhavani Sudha <bh...@gmail.com>.
+1 great idea.
On Wed, Jan 8, 2020 at 1:20 PM Shiyan Xu <xu...@gmail.com>
wrote:
> +1. Good idea for testing phase.
>
> On Wed, 8 Jan 2020, 08:26 Vinoth Chandar, <vi...@apache.org> wrote:
>
> > +1 one More week to land two weeks of testing is a good plan
> >
> > On Wed, Jan 8, 2020 at 2:41 AM leesf <le...@gmail.com> wrote:
> >
> > > Dear Community,
> > >
> > > As discussed before[1], the proposed release date of *end of Jan* for
> > Hudi
> > > 0.5.1 is getting closer. And we have many bug fixes and features[2]
> since
> > > the first release about three months ago.
> > >
> > > To make the release version more stable, I would suggest a bug fixing
> and
> > > testing period of two weeks to be on the safe side. Given the testing
> > > period, I would propose to do the code freeze on the 15th of Jan 23:59
> > PST
> > > in order to keep the release date. It means that we would cut the Hudi
> > > 0.5.1 release branch on this date and no more feature contributions
> would
> > > be accepted for this branch. And the uncompleted features would be
> > shipped
> > > with next release.
> > >
> > > There are 25 jira issues unfinished[3] yet, and you would still pick up
> > the
> > > issues you are interested, among all issues, the major issues would be
> > > update to spark2.4[4], Replace Databricks spark-avro with native
> > > spark-avro[5] and Migrating to Scala 2.12[6], which are important for
> > > runing Hudi on Google Cloud, and we incline to get them on land.
> > >
> > > What do you think about the proposed code freeze date? Glad to hear
> your
> > > thoughts.
> > >
> > > Best,
> > > Leesf
> > >
> > > [1]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
> > > [2]
> > >
> > >
> >
> https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
> > > [3]
> > >
> > >
> >
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
> > > [4] https://issues.apache.org/jira/browse/HUDI-12
> > > [5] https://issues.apache.org/jira/browse/HUDI-91
> > > [6] https://issues.apache.org/jira/browse/HUDI-238
> > >
> >
>
Re: [DISCUSS] Code freeze date for next release(0.5.1)
Posted by Shiyan Xu <xu...@gmail.com>.
+1. Good idea for testing phase.
On Wed, 8 Jan 2020, 08:26 Vinoth Chandar, <vi...@apache.org> wrote:
> +1 one More week to land two weeks of testing is a good plan
>
> On Wed, Jan 8, 2020 at 2:41 AM leesf <le...@gmail.com> wrote:
>
> > Dear Community,
> >
> > As discussed before[1], the proposed release date of *end of Jan* for
> Hudi
> > 0.5.1 is getting closer. And we have many bug fixes and features[2] since
> > the first release about three months ago.
> >
> > To make the release version more stable, I would suggest a bug fixing and
> > testing period of two weeks to be on the safe side. Given the testing
> > period, I would propose to do the code freeze on the 15th of Jan 23:59
> PST
> > in order to keep the release date. It means that we would cut the Hudi
> > 0.5.1 release branch on this date and no more feature contributions would
> > be accepted for this branch. And the uncompleted features would be
> shipped
> > with next release.
> >
> > There are 25 jira issues unfinished[3] yet, and you would still pick up
> the
> > issues you are interested, among all issues, the major issues would be
> > update to spark2.4[4], Replace Databricks spark-avro with native
> > spark-avro[5] and Migrating to Scala 2.12[6], which are important for
> > runing Hudi on Google Cloud, and we incline to get them on land.
> >
> > What do you think about the proposed code freeze date? Glad to hear your
> > thoughts.
> >
> > Best,
> > Leesf
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
> > [2]
> >
> >
> https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
> > [3]
> >
> >
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
> > [4] https://issues.apache.org/jira/browse/HUDI-12
> > [5] https://issues.apache.org/jira/browse/HUDI-91
> > [6] https://issues.apache.org/jira/browse/HUDI-238
> >
>
Re: [DISCUSS] Code freeze date for next release(0.5.1)
Posted by Vinoth Chandar <vi...@apache.org>.
+1 one More week to land two weeks of testing is a good plan
On Wed, Jan 8, 2020 at 2:41 AM leesf <le...@gmail.com> wrote:
> Dear Community,
>
> As discussed before[1], the proposed release date of *end of Jan* for Hudi
> 0.5.1 is getting closer. And we have many bug fixes and features[2] since
> the first release about three months ago.
>
> To make the release version more stable, I would suggest a bug fixing and
> testing period of two weeks to be on the safe side. Given the testing
> period, I would propose to do the code freeze on the 15th of Jan 23:59 PST
> in order to keep the release date. It means that we would cut the Hudi
> 0.5.1 release branch on this date and no more feature contributions would
> be accepted for this branch. And the uncompleted features would be shipped
> with next release.
>
> There are 25 jira issues unfinished[3] yet, and you would still pick up the
> issues you are interested, among all issues, the major issues would be
> update to spark2.4[4], Replace Databricks spark-avro with native
> spark-avro[5] and Migrating to Scala 2.12[6], which are important for
> runing Hudi on Google Cloud, and we incline to get them on land.
>
> What do you think about the proposed code freeze date? Glad to hear your
> thoughts.
>
> Best,
> Leesf
>
> [1]
>
> https://cwiki.apache.org/confluence/display/HUDI/20191210+Weekly+Sync+Minutes
> [2]
>
> https://issues.apache.org/jira/browse/HUDI-507?jql=project%20%3D%20HUDI%20AND%20fixVersion%20%3D%200.5.1
> [3]
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+HUDI+AND+fixVersion+%3D+0.5.1+AND+status+%21%3D+Fixed++AND+status+%21%3D+Resolved+AND+status+%21%3D+Closed+&tempMax=1000
> [4] https://issues.apache.org/jira/browse/HUDI-12
> [5] https://issues.apache.org/jira/browse/HUDI-91
> [6] https://issues.apache.org/jira/browse/HUDI-238
>