[
https://issues.apache.org/jira/browse/CASSANDRA-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078523#comment-18078523
]
Brandon Williams commented on CASSANDRA-20672:
----------------------------------------------
bq. So i don't see the need for this improvement.
...
bq. Apart from the hassle of having to edit the debian/changelog
That is indeed the hassle that has brought us here. Once you are in this state
you currently have two options: manually edit the changelog and remove the
entry, just so dch can put that same entry back in, rather than error out. Or
you can hack the script to comment out dch (since everything is already
correct), which is what [~rishabhsaraswat]'s patch is formalizing. From the
standpoint of release managers that have been in the situation, I think that
counts as progress.
+1 from me and committed.
> release scripts should allow skipping the changelog update
> ----------------------------------------------------------
>
> Key: CASSANDRA-20672
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20672
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Build
> Reporter: Brandon Williams
> Assignee: Rishabh Saraswat
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 6.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If the release script fails for whatever reason, you can remove the deployed
> files from svn and drop the maven artifact to start again, but one last step
> you can't undo is the changelog since it's already committed. In these cases
> I comment out the 'dch' in the script so I can make another attempt, but it
> would be good to have a proper flag for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
