[jira] [Comment Edited] (CALCITE-4881) Calcite release tags should have rel/... prefix as per the ASF requirements

["Francis Chuang (Jira)" <ji...@apache.org>]

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

Francis Chuang edited comment on CALCITE-4881 at 11/9/21, 6:39 AM:
-------------------------------------------------------------------

If we do this for `avatica-go` it will break go modules as it expects versions to be tagged as `v.X.Y.Z` see https://golang.org/doc/modules/publishing#publishing-steps

If we create a tag for `rel/v.X.Y.Z` for in the avatica-go repo, go modules will assume that we're publishing a module under the rel folder, which will break things.

Is this a hard requirement for all Apache repositories?


was (Author: francischuang):
If we do this for `avatica-go` it will break go modules as it expects versions to be tagged as `v.X.Y.Z` see https://golang.org/doc/modules/publishing#publishing-steps

Is this a hard requirement for all Apache repositories?

> Calcite release tags should have rel/... prefix as per the ASF requirements
> ---------------------------------------------------------------------------
>
>                 Key: CALCITE-4881
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4881
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Vladimir Sitnikov
>            Priority: Critical
>
> As per "Git status update" mail from Infra, release commits should be tagged with rel/... tags which are protected at the Infra side so they can't be overwritten, removed, etc.
> See sample: ACCUMULO-4106



--
This message was sent by Atlassian Jira
(v8.20.1#820001)