You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by Gabor Szadovszky <ga...@apache.org> on 2019/10/30 13:02:50 UTC
release process - using rc tags
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
Re: release process - using rc tags
Posted by Gabor Szadovszky <ga...@apache.org>.
Thanks everyone for the support.
I've created the jira PARQUET-1687
<https://issues.apache.org/jira/browse/PARQUET-1687> to track this and also
3 PRs for the site <https://github.com/apache/parquet-site/pull/2>, mr
<https://github.com/apache/parquet-mr/pull/697> and format
<https://github.com/apache/parquet-format/pull/155> repos.
There is also a PR for site <https://github.com/apache/parquet-site/pull/1>
which is related to the releasing policy.
Could you please check them out so we can step forward with the release?
Cheers,
Gabor
P.S. Thanks, Ryan for the link of the Iceberg release process. It was
very helpful. Meanwhile, I've discovered a bug in it
<http://iceberg.apache.org/how-to-release/#finishing-the-release>. After
adding the tag it does not say to push it. Without pushing the tag it will
only be available locally.
On Fri, Nov 1, 2019 at 3:44 PM Anna Szonyi <sz...@gmail.com> wrote:
> +1
>
> On Thu, Oct 31, 2019 at 2:30 AM Junjie Chen <ch...@gmail.com>
> wrote:
>
> > +1
> >
> > XU Qinghui <qi...@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
> > <zi...@cloudera.com.invalid>
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Wed, Oct 30, 2019 at 2:03 PM Gabor Szadovszky <
> gabor@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
> > > > >
> > > >
> >
>
Re: release process - using rc tags
Posted by Anna Szonyi <sz...@gmail.com>.
+1
On Thu, Oct 31, 2019 at 2:30 AM Junjie Chen <ch...@gmail.com>
wrote:
> +1
>
> XU Qinghui <qi...@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
> <zi...@cloudera.com.invalid>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Wed, Oct 30, 2019 at 2:03 PM Gabor Szadovszky <gabor@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
> > > >
> > >
>
Re: release process - using rc tags
Posted by Junjie Chen <ch...@gmail.com>.
+1
XU Qinghui <qi...@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 <zi...@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
> > >
> >
Re: release process - using rc tags
Posted by XU Qinghui <qi...@gmail.com>.
+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 <zi...@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
> >
>
Re: release process - using rc tags
Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
+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 <zi...@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
>
Re: release process - using rc tags
Posted by 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 <zi...@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
Re: release process - using rc tags
Posted by Zoltan Ivanfi <zi...@cloudera.com.INVALID>.
+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