[
https://issues.apache.org/jira/browse/ZOOKEEPER-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli updated ZOOKEEPER-3695:
---------------------------------------
Description:
During the release of 3.6.0, rc0, I noticed that the source tarball differs
from the repository:
- there is no "dev/docker" directory (so we are missing a part of the codebase,
even this is not so important)
- there is no "zookeeper-metrics-providers" directory (so the project is not
buildable)
- the c client directory contains temporary files (so we are including
'binaries')
I have also noted that NOTICE file report 2019 and it should be 2020
was:
During the release of 3.6.0, rc0, I noticed that the source tarball differs
from the repository:
- there is no "dev/docker" directory (so we are missing a part of the codebase,
even this is not so important)
- there is no "zookeeper-metrics-providers" directory (so the project is not
buildable)
- the c client directory contains temporary files (so we are including
'binaries')
-
> Source release tarball does not match repository in 3.6.0
> ---------------------------------------------------------
>
> Key: ZOOKEEPER-3695
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3695
> Project: ZooKeeper
> Issue Type: Task
> Components: build
> Affects Versions: 3.6.0
> Reporter: Enrico Olivelli
> Assignee: Enrico Olivelli
> Priority: Blocker
> Fix For: 3.6.0
>
>
> During the release of 3.6.0, rc0, I noticed that the source tarball differs
> from the repository:
> - there is no "dev/docker" directory (so we are missing a part of the
> codebase, even this is not so important)
> - there is no "zookeeper-metrics-providers" directory (so the project is not
> buildable)
> - the c client directory contains temporary files (so we are including
> 'binaries')
> I have also noted that NOTICE file report 2019 and it should be 2020
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
