hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zhanwei Wang <wan...@apache.org>
Subject Re: libhdfs3 development is still going on outside of ASF
Date Fri, 16 Sep 2016 08:18:40 GMT
Hi Roman

I have create JIRA HAWQ-1058 to track the release of libhdfs3 tarball and HAWQ-1059 to separate
it as new ASF repository and set the tag of backlog. 

I also update the readme of current libhdfs3’s Github repository in order to declare it
is in read only mode and let its user know where it is going to. Hope they would not get lost.

https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3/commit/59789c90f2f42726900eb2e417eea88a670f0b3c
<https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3/commit/59789c90f2f42726900eb2e417eea88a670f0b3c>



Best Regards

Zhanwei Wang
wangzw@apache.org



> 在 2016年9月16日,下午3:40,Zhanwei Wang <wangzw@apache.org> 写道:
> 
>> Now, that is NOT to say that when you DO release you shouldn't be producing
>> multiple source tarballs. That's more than appropriate and will give your users
>> maximum benefit on both HAWQ and libhdfs3 side of things.
> 
> 
> Release separated tarball for libhdfs3 would be much better for libhdfs3 users to access
the code.  
> 
> 
>> you guys can't quite master the release process yet. Splitting the project
>> into multiple repos will only make it worse. Master the release mechanics
>> and then we can talk about multiple repos.
> 
> 
> HAWQ has got enough difficulties for its release. I agree with you that we separate repository
for libhdfs3 after HAWQ establish the release process. And when it is done, the result is
good to both ASF and libhdfs3’s users.
> 
> 
> Best Regards
> 
> Zhanwei Wang
> wangzw@apache.org
> 
> 
> 
>> 在 2016年9月16日,下午1:20,Roman Shaposhnik <roman@shaposhnik.org>
写道:
>> 
>> On Wed, Sep 14, 2016 at 11:38 PM, Zhanwei Wang <wangzw@apache.org <mailto:wangzw@apache.org>>
wrote:
>>> Hi Roman
>>> 
>>> I think I have discussed enough about the benefit and drawback of merge two independent
project together.
>>> Let me propose a way to see if it can make both ASF and libhdfs3’s user happy.
And I need your advise.
>>> 
>>> 
>>> Is it possibile to have two git repository in ASF for HAWQ incubator project.
If it is possible, I propose to solve the libhdfs3 issue like this.
>>> 
>>> 1) create a new git repository in ASF and push all libhdfs3’s code and branch
from Github to ASF.
>>> 2) make libhdfs3’s Github repository as read only mirror of ASF repository.
Maybe need to transfer current owner of Github repository from Pivotal to ASF on Github.
>>> 3) HAWQ keep the stable version code of libhdfs3 or just Git reference.
>>> 
>>> 
>>> In this way, we keep libhdfs3 independent and keep its all pull request, wiki,
issues and history. And most importantly libhdfs3 can follow ASF rules and process. People
can file pull request on Github and commit to ASF repository and eventually mirror to Github.
>>> 
>>> 
>>> Any comments?
>> 
>> It is possible, but at this point I will strongly recommend against
>> it. As it is,
>> you guys can't quite master the release process yet. Splitting the project
>> into multiple repos will only make it worse. Master the release mechanics
>> and then we can talk about multiple repos.
>> 
>> Now, that is NOT to say that when you DO release you shouldn't be producing
>> multiple source tarballs. That's more than appropriate and will give your users
>> maximum benefit on both HAWQ and libhdfs3 side of things.
>> 
>> Thanks,
>> Roman.
> 
> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message