[ 
https://issues.apache.org/jira/browse/GEODE-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291391#comment-17291391
 ] 

ASF subversion and git services commented on GEODE-8481:
--------------------------------------------------------

Commit 83bd74869e9cf39e31f4c80043e73c1458a4a14e in geode's branch 
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=83bd748 ]

GEODE-8481: fix a few release script issues (#5899)

* placeholder for branching from specific SHA if necessary
* commit message including build number is needlessly confusing (and 
potentially misleading since build number comes from pipeline)
* remove release scripts from created support branch to avoid confusion
* update all copyrights not just top-level notice
* adjust Version to KnownVersion going forward
* run expected-file tests after dependency bumps as transitive resolutions 
could have changed
* full checkout for geode-develop to ensure we get all tags
* always generate sha (it is needed later even if not doing brew)
* don't create nested tags
* fix printing of removed releases
* skip prompt to manually perform brew steps for non-latest releases
* add docker tag to docker test command if not latest release
* as per PR#6050 don't add new commandset for new minor, instead add new 
constructor param to retain last client serialization version

> fix rc pipeline to work with Liberica image
> -------------------------------------------
>
>                 Key: GEODE-8481
>                 URL: https://issues.apache.org/jira/browse/GEODE-8481
>             Project: Geode
>          Issue Type: Bug
>          Components: release
>            Reporter: Owen Nichols
>            Assignee: Owen Nichols
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.14.0
>
>
> changes for GEODE-8321 resulted in missing dependencies in the rc pipeline 
> such as git, unzip, and ssh-keygen.  Add these back in and fix any other 
> issues encountered during 1.13.0 release process.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to