Patrick Hunt commented on ZOOKEEPER-224:

Thanks for the feedback Doug, I hadn't thought of that but it makes sense.

I definitely think we should support this, but it's quickly turning from extra 
work for me, to a lot of extra work. ;-)

I talked with Nigel who's the release manager for Hadoop Core. There is recent 
progress on 
https://issues.apache.org/jira/browse/HADOOP-3305 which is very similar to this 

Nigel mentioned that we should be able to get some time from the contributors 
to core's build management. We currently use the hadoop core build/release 
process, it's a huge benefit to me not to have to reinvent the wheel and just 
use their vetted processes. I'll talk with Nigel to see what can be done wrt 
getting the work from 3305 "ported" into ZK build/release process. I'm going to 
hold off on any changes related to this issue (build or release) until 3305 
settles, worst case we can port the work from 3305 ourselves.

> Deploy ZooKeeper 3.0.0 to a Maven Repository
> --------------------------------------------
>                 Key: ZOOKEEPER-224
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224
>             Project: Zookeeper
>          Issue Type: Task
>          Components: build
>    Affects Versions: 3.0.0
>            Reporter: Hiram Chirino
>            Assignee: Patrick Hunt
>            Priority: Critical
> I've created the maven poms needed for the 3.0.0 release.  
> The directory structure and artifacts located at:
> http://people.apache.org/~chirino/zk-repo/
> aka
> people.apache.org:/x1/users/chirino/public_html/zk-repo
> Just need sto get GPG signed by the project KEY and deployed to:
> people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository
> Who's the current ZooKeeper release manager?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to