+1
XU Qinghui <qinghui...@gmail.com> 于2019年10月31日周四 上午6:35写道： > > +1 > > Le mer. 30 oct. 2019 à 16:53, Driesprong, Fokko <fo...@driesprong.frl> a > écrit : > > > +1 > > > > Op wo 30 okt. 2019 om 16:51 schreef Ryan Blue <rb...@netflix.com.invalid>: > > > > > +1 > > > > > > I recently built the release process for Iceberg and that's what we > > decided > > > to go with in that community. Here are the docs if you'd like to copy > > them > > > to update the Parquet docs: > > > http://iceberg.apache.org/how-to-release/#finishing-the-release > > > > > > rb > > > > > > On Wed, Oct 30, 2019 at 6:19 AM Zoltan Ivanfi <z...@cloudera.com.invalid> > > > wrote: > > > > > > > +1 > > > > > > > > On Wed, Oct 30, 2019 at 2:03 PM Gabor Szadovszky <ga...@apache.org> > > > wrote: > > > > > > > > > > Dear All, > > > > > > > > > > Our current tagging policy in the release process requires to use the > > > > same > > > > > tag for all the release candidates which means at RC2 we remove the > > tag > > > > > from RC1 head and adds again to the RC2 head and so on. I think it is > > > > not a > > > > > good practice. Hard to track RCs and rewriting git history is usually > > > > not a > > > > > good idea. > > > > > If there are no objections, I'll update the related scripts and docs > > so > > > > we > > > > > will create RC tags (e.g. apache-parquet-1.11.0-rc6) first and add > > the > > > > > final release tag (e.g. apache-parquet-1.11.0) after the vote passes. > > > > > > > > > > Regards, > > > > > Gabor > > > > > > > > > > > > > -- > > > Ryan Blue > > > Software Engineer > > > Netflix > > > > >
