I have fresh news while working on the issue https://issues.apache.org/jira/browse/ZOOKEEPER-3695
I saw that Maven already did a better way automatically other then what we were trying to achieve with the maven-assembly-plugin By default using the Apache Maven Parent Pom (we are using it as we are an ASF project) Maven creates a "sources" zip and this package is a perfect copy of the git repository during the release process. I have addeded in the staging directory the zip file, signature and the sha512 hash (already created during the automatic release procedure) http://home.apache.org/~eolivelli/zookeeper-3.6.0-candidate-0/ If we agree on changing the format of the "source release" from tar.gz to zip then the staged rc is good for a VOTE and it is perfectly integrated with the Maven release procedure. Thoughts ? Enrico Il giorno sab 11 gen 2020 alle ore 22:54 Enrico Olivelli < eolive...@gmail.com> ha scritto: > Hi, > I was preparing the first rc of 3.6.0 but unfortunately it failed as I > have found a blocker issue > > This is the issue > https://issues.apache.org/jira/browse/ZOOKEEPER-3695 > > The short version of the story is that the source tarbal does not reflect > the git repository, some directories are missing and there is some curn in > the c client. > > I am working on a fix > > Meanwhile....if you have cycles it would be very helpful if you take a > look to the staged artifacts of 3.6.0-rc0. > > you can find them here: > http://home.apache.org/~eolivelli/zookeeper-3.6.0-candidate-0/ > > the Maven staging repository is; > https://repository.apache.org/content/repositories/orgapachezookeeper-1045 > > I won't call for a vote for 3.6.0-rc0. > > The first call will be for 3.6.0-rc1 as I have already created a tag for > release-3.6.0-0 and I don't want to mess up the repository of anyone who > already "git fetched" the tag. > https://github.com/apache/zookeeper/commits/release-3.6.0-0 > > Stay tuned > > Enrico > >
