Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
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.
