[
https://issues.apache.org/jira/browse/DAFFODIL-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-2518.
--------------------------------------
Resolution: Fixed
Fixed in commit d2c151ff9a888bda16e73ebaca00c2dc94ad5e34
> Minor fixes required to release candidate script
> ------------------------------------------------
>
> Key: DAFFODIL-2518
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2518
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Priority: Minor
> Fix For: 3.2.0
>
>
> Some issues were found when building an rc2 for 3.1.0:
> - Typo in "*Comitting* Site Changes"
> - Because of the *set -e*, if a command ever exits with a non-zero exit code,
> the release candidate script just stops, and it's not obvious there was a
> failure. We should trap ERR and print out a message to make it clear things
> failed and what steps to take
> - When the script commits site changes, it's possible for no changes to exist
> (this is likely in an rc2 since all documentation has already been committed
> during rc1). When this happens, the git commit command exists with a non-zero
> exit code and stop processing
> - The script says to "Delete" staged files at repository.apache.org, but
> "Drop" is the correct terminology
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
