[
https://issues.apache.org/jira/browse/CASSANDRA-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045429#comment-18045429
]
Michael Semb Wever commented on CASSANDRA-20672:
------------------------------------------------
The commit hasn't been pushed to branches yet, only to the tag and that needs
to be deleted anyway.
So i don't see the need for this improvement.
Apart from the hassle of having to edit the debian/changelog (something that
could be automated i believe– as it only
[lists|https://github.com/apache/cassandra/blob/cassandra-5.0/debian/changelog]
maintainer and timestamp).
Even more ideal would be to remove debian/changelog from git altogether, but
then we need to automate it and move it into the debian packaging scripts, as
building debian packages source release SHAs must reproduce matching build
artefacts.
> 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, 5.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]
