[
https://issues.apache.org/jira/browse/GEODE-10149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510898#comment-17510898
]
ASF subversion and git services commented on GEODE-10149:
---------------------------------------------------------
Commit d5e3663a89c9346734711e846dc651d391a958d2 in geode's branch
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d5e3663 ]
GEODE-10149: Don't reset custom radish baseline on a patch release (#7472)
* GEODE-10149: don't reset radish baseline prematurely
radish benchmarks use a custom branch/tag
on a new minor, the release scripts should reset that to the new minor release
however, the scripts were incorrectly resetting it on every patch, oops
if custom baseline on develop is newer [than release branch cut date],
resetting might still be the wrong choice. but, assuming it's older, a new
minor is the right time to un-custom it. hopefully PR review catches situation
where the recommended change is not wanted...the alternative of not doing it by
default seems much more likely to result in forgetting about it altogether
> don't reset radish benchmark baseline on a patch release
> --------------------------------------------------------
>
> Key: GEODE-10149
> URL: https://issues.apache.org/jira/browse/GEODE-10149
> Project: Geode
> Issue Type: Task
> Components: release
> Reporter: Owen Nichols
> Assignee: Owen Nichols
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> radish benchmarks use a custom branch/tag
> on a new minor, the release scripts should reset that to the new minor release
> however, the scripts are incorrectly resetting it on every patch, oops
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
