[jira] [Commented] (PARQUET-1687) Update release process

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PARQUET-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967630#comment-16967630 ] 

ASF GitHub Bot commented on PARQUET-1687:
-----------------------------------------

gszadovszky commented on pull request #697: PARQUET-1687: Update release process
URL: https://github.com/apache/parquet-mr/pull/697
 
 
   Update prepare-release.sh to create RC tags and keep using the current
   RC version with SNAPSHOT for development.
   Update source-release.sh to retrieve the hash of the RC tag.
   Create the new script finalize-release to create the final release tag
   and update the development version.
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Update release process
> ----------------------
>
>                 Key: PARQUET-1687
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1687
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-format, parquet-mr, parquet-site
>            Reporter: Gabor Szadovszky
>            Assignee: Gabor Szadovszky
>            Priority: Major
>              Labels: pull-request-available
>
> 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. It is not a good practice. Hard to track RCs and rewriting git history is usually not a good idea.
> 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.
> It is also very confusing that we always use SNAPSHOT version of the next release even if the previous one is not released yet. For example we have not released {{1.11.0}} yet (we are after the failed vote of 1.11.0-rc6) still, we use the version number {{1.12.0-SNAPSHOT}}. This is very confusing.
> Update the release scripts and docs to use the same {{SNAPSHOT}} version at RC phase and only step to the next version number after the vote passed and the final release tag is added.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)