GitHub user hansva added a comment to the discussion: Clarification needed: Release process and tagging strategy for stable releases
Hi @rahulduvedi , You are correct, we do not create an extra tag for the actual release, the RC that is voted on and accepted during the voting process is turned into the final release artifact. For ASF projects, the **ONLY** official source is the one that can be found at the [central archive](https://downloads.apache.org/hop/). But this source code should match the tag in GitHub. Technically, we vote on a commit hash and not on a tag, but a tag is added to make everyone's life simpler. You can follow the process on our [mailing list](https://lists.apache.org/[email protected]) here you can see that we started voting on the 2.15.0-rc1 tag on August 8. Due to a blocking issue, that vote was canceled, and we created rc2, which has passed the vote and was turned into the official release today. All Docker images and other artifacts are based of that commit/tag. We could change the process and add another tag to the RC that is turned into the release, but that would always just be the final RC tag. Hope this helps GitHub link: https://github.com/apache/hop/discussions/5630#discussioncomment-14151071 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
