[
https://issues.apache.org/jira/browse/DERBY-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603353#comment-13603353
]
Rick Hillegas commented on DERBY-5463:
--------------------------------------
Hi Myrna,
Can you give more information about this problem? The release script updates
release.properties twice:
1) At the beginning, the script prompts for the new release id. This is written
to release.properties.
2) At the end, the script bumps the last digit of the release id in
release.properties.
Did the release manager give a correct release id in step (1) but the script
somehow corrupted it? Or did the script faithfully do what the release manager
directed? Thanks.
> ant release should not modify drdamaint version
> ------------------------------------------------
>
> Key: DERBY-5463
> URL: https://issues.apache.org/jira/browse/DERBY-5463
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.8.2.2, 10.9.1.0
> Reporter: Myrna van Lunteren
> Priority: Minor
>
> ant release automatically sets drdamaint version to 0 in release.properties.
> However, on the 10.8 branch, drdamaint version had been increased to trigger
> a difference in behavior with vs. without a particular check in; ant release
> caused this to get reset thus breaking the fix.
> ant release should somehow assess the value of drdamaint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
