I think we are creating unnecessary bureaucratic hurdles here by preventing
contrib project from having a branch. I don't see why zebra has to use pig
release branch, as the new pig release does not include it.
The decisions are supposed to help keeping things open, but this seems to be
forcing Ra
Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent: Tuesday, August 18, 2009 9:49 AM
To: pig-dev@hadoop.apache.org
Subject: Re: Proposal to create a branch for contrib project Zebra
Milind A Bhandarkar wrote:
Since zebra.jar is not included in pig.jar (I hope not), I can still
@hadoop.apache.org
Subject: Re: Proposal to create a branch for contrib project Zebra
Milind A Bhandarkar wrote:
>
> Since zebra.jar is not included in pig.jar (I hope not), I can still
use
> stable zebra jar (binary) with latest pig compiled in trunk.
The problem is that though the curren
Milind A Bhandarkar wrote:
Since zebra.jar is not included in pig.jar (I hope not), I can still use
stable zebra jar (binary) with latest pig compiled in trunk.
The problem is that though the current version is "expected to be"
stable, it would still require some bug fixes. We essentially nee
Raghu,
Since most of the bugfixes to Pig happen in trunk, I (and several folks that
I know) tend to use pig trunk most often. It would be nice if I picked up
Zebra enhancements along the way, as well.
Since zebra.jar is not included in pig.jar (I hope not), I can still use
stable zebra jar (bina
Raghu Angadi wrote:
Hi Santosh,
There are two separate things :
(a) voting a contributor as a committer
(b) committing to a contrib project.
[...]
Reason for (a) is simple scalability. We can not monitor everything. If
I meant to say "Reason for (b)" (why contrib commits are treated bi
The reason for a branch is purely based on fair number of improvements
we are planning for Zebra and our desire to have a stable Zebra
implementation for users to use along with PIG on Hadoop-0.20.
New features planned (jiras will be filed soon) :
* Column security (different permissions f
Hi Santosh,
There are two separate things :
(a) voting a contributor as a committer
(b) committing to a contrib project.
(b):
My experience with Hadoop is that "Contrib" by definition is very
loosely coupled with core. By convention, we as committers to core
(hdfs, mapred, etc) did not hav
-dev@hadoop.apache.org
Subject: Re: Proposal to create a branch for contrib project Zebra
IANAC, but my (non-binding) vote is also -1. I think all the
improvements
and feature addition to zebra should be available through pig trunk. The
codebase is not big enough to justify creating a branch. If
That leaves us with contrib committers.
Can you point to earlier email threads that cover the topic of giving
committer access to contrib projects? Specifically, what does it
mean to
award someone committer privileges to a contrib project, what are the
access privileges that come with such ri
e dos/don'ts,
etc.
Thirdly, are there instances of contrib committers creating branches?
Thanks,
Santhosh
-Original Message-
From: Arun C Murthy [mailto:a...@yahoo-inc.com]
Sent: Monday, August 17, 2009 6:18 PM
To: pig-dev@hadoop.apache.org
Subject: Re: Proposal to create a branch f
On Aug 17, 2009, at 4:38 PM, Santhosh Srinivasan wrote:
Is there any precedence for such proposals? I am not comfortable with
extending committer access to contrib teams. I would suggest that
Zebra
be made a sub-project of Hadoop and have a life of its own.
There has been sufficient prece
precedent.
Santhosh
-Original Message-
From: Olga Natkovich
Sent: Monday, August 17, 2009 5:37 PM
To: Santhosh Srinivasan; 'pig-dev@hadoop.apache.org'
Subject: RE: Proposal to create a branch for contrib project Zebra
Over time the plan is to move Zebra to a subproject. Unt
, August 17, 2009 5:27 PM
To: Olga Natkovich; 'pig-dev@hadoop.apache.org'
Subject: RE: Proposal to create a branch for contrib project Zebra
Its good to know that Raghu Angadi is a PMC member and that he has
committer rights to all subprojects. That's besides the point.
The example
IANAC, but my (non-binding) vote is also -1. I think all the improvements
and feature addition to zebra should be available through pig trunk. The
codebase is not big enough to justify creating a branch. If the reason is
Pig's dependence on a checked in hadoop jar, the shims proposal by Dmitry
shou
From: Santhosh Srinivasan [mailto:s...@yahoo-inc.com]
Sent: Monday, August 17, 2009 4:39 PM
To: Santhosh Srinivasan; pig-dev@hadoop.apache.org
Subject: RE: Proposal to create a branch for contrib project Zebra
My vote is -1
-Original Message-
From: Santhosh Srinivasan
Sent: Monday, Au
+1
On 8/18/09 7:11 AM, "Olga Natkovich" wrote:
> +1
>
> -Original Message-
> From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
> Sent: Monday, August 17, 2009 4:06 PM
> To: pig-dev@hadoop.apache.org
> Subject: Proposal to create a branch for contrib project Zebra
>
>
> Thanks to the
...@yahoo-inc.com]
Sent: Monday, August 17, 2009 4:39 PM
To: Santhosh Srinivasan; pig-dev@hadoop.apache.org
Subject: RE: Proposal to create a branch for contrib project Zebra
My vote is -1
-Original Message-
From: Santhosh Srinivasan
Sent: Monday, August 17, 2009 4:38 PM
To: 'pi
Is there any precedence for such proposals? I am not comfortable with
extending committer access to contrib teams. I would suggest that Zebra
be made a sub-project of Hadoop and have a life of its own.
Santhosh
-Original Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent: M
My vote is -1
-Original Message-
From: Santhosh Srinivasan
Sent: Monday, August 17, 2009 4:38 PM
To: 'pig-dev@hadoop.apache.org'
Subject: RE: Proposal to create a branch for contrib project Zebra
Is there any precedence for such proposals? I am not comfortable with
extending
+1
-Original Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent: Monday, August 17, 2009 4:06 PM
To: pig-dev@hadoop.apache.org
Subject: Proposal to create a branch for contrib project Zebra
Thanks to the PIG team, The first version of contrib project Zebra
(PIG-833) is com
21 matches
Mail list logo
