[
https://issues.apache.org/jira/browse/CASSANDRA-18367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18367:
-----------------------------------------
Description: Currently the release scripts are two monolithic scripts:
prepare_releash.sh, and finish_release.sh. If any step in either of the
scripts fails, you are left with a state that requires manual resolution,
generally by script dissection. It would be easier to handle these scenarios
if each step were defined in discrete files that the prepare/finish wrapper
then called. (was: Currently the release scripts are two monolithic scripts:
prepare_releash.sh, and finish_release.sh. If any step in either of the
scripts fails, you are left with a state that requires manually resolution,
generally by script dissection. It would be easier to handle these scenarios
if each step were defined in discrete files that the prepare/finish wrapper
then called.)
> Separate release scripts into discrete steps
> --------------------------------------------
>
> Key: CASSANDRA-18367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18367
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Currently the release scripts are two monolithic scripts: prepare_releash.sh,
> and finish_release.sh. If any step in either of the scripts fails, you are
> left with a state that requires manual resolution, generally by script
> dissection. It would be easier to handle these scenarios if each step were
> defined in discrete files that the prepare/finish wrapper then called.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
