You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Enrico Olivelli (Jira)" <ji...@apache.org> on 2020/04/15 14:19:00 UTC
[jira] [Resolved] (ZOOKEEPER-3635) Use Docker and Maven Release
Plugin to prepare ZooKeeper releases
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enrico Olivelli resolved ZOOKEEPER-3635.
----------------------------------------
Resolution: Fixed
> Use Docker and Maven Release Plugin to prepare ZooKeeper releases
> ------------------------------------------------------------------
>
> Key: ZOOKEEPER-3635
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3635
> Project: ZooKeeper
> Issue Type: Task
> Components: build
> Affects Versions: 3.6.0
> Reporter: Enrico Olivelli
> Assignee: Enrico Olivelli
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> In 3.5.5 and 3.5.6 we followed a new release procedure based on Maven:
> [https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+maven]
> That procedure needed some "manual" parts to change the project version inside pom files and also inside the sources of the C Client.
> We can automate more and more in order to make the release procedure mostly automatic.
> We should also use 'docker' in order to have a reproducible build environment, expectially for the 'convenience binaries':
> * Java version (we want to build the project with Java 8 in 3.6.0)
> * C client (tools, system headers and openssl version)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)