[
https://issues.apache.org/jira/browse/SPARK-28496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin reassigned SPARK-28496:
--------------------------------------
Assignee: Dongjoon Hyun
> Use branch name instead of tag during dry-run
> ---------------------------------------------
>
> Key: SPARK-28496
> URL: https://issues.apache.org/jira/browse/SPARK-28496
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 3.0.0
> Reporter: Dongjoon Hyun
> Assignee: Dongjoon Hyun
> Priority: Minor
>
> There are two cases when we use `dry run`.
> First, when the tag already exists, we can ask `confirmation` on the existing
> tag name.
> {code}
> $ dev/create-release/do-release-docker.sh -d /tmp/spark-2.4.4 -n -s docs
> Output directory already exists. Overwrite and continue? [y/n] y
> Branch [branch-2.4]:
> Current branch version is 2.4.4-SNAPSHOT.
> Release [2.4.4]: 2.4.3
> RC # [1]:
> v2.4.3-rc1 already exists. Continue anyway [y/n]? y
> This is a dry run. Please confirm the ref that will be built for testing.
> Ref [v2.4.3-rc1]:
> {code}
> Second, when the tag doesn't exist, we had better ask `confirmation` on the
> branch name.
> {code}
> $ dev/create-release/do-release-docker.sh -d /tmp/spark-2.4.4 -n -s docs
> Branch [branch-2.4]:
> Current branch version is 2.4.4-SNAPSHOT.
> Release [2.4.4]:
> RC # [1]:
> This is a dry run. Please confirm the ref that will be built for testing.
> Ref [v2.4.4-rc1]:
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
