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

Francis Chuang commented on CALCITE-5097:
-----------------------------------------

I just did a dry-run release and it worked properly as 
stage-vote-release-plugin does not need to know about the default branch.

Copying from [my 
email|https://lists.apache.org/thread/drb5wv8vskk82xqrz57s08jxnf17wxyo] to the 
dev list:
{quote}Quick update. I just did a dry-run release for Avatica and it built fine
without needing to set the branch in vlsi-release-plugin's configuration.

The plugin only pushes tags to git and I don't think it ever commits any
files, so I don't think it needs to know about us renaming our default
branch to main. I also ran `git branch -a` in my local copy of Avatica
and I don't see any branch or references to "master" after running a
dry-run release.{quote}

> Release Avatica 1.21.0
> ----------------------
>
>                 Key: CALCITE-5097
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5097
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Francis Chuang
>            Priority: Major
>             Fix For: avatica-1.21.0
>
>
> Release Avatica 1.21.0.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to