“Adoption of new codebase” clause does apply to “creation of new sub-projects
within the project”, and needs 2/3 of PMC.
That vote has already passed, in vote thread
https://s.apache.org/HDDSMergeResult. Therefore, we already have a subproject.
Now, we want to add code to this subproject by merging this branch, therefore
this is treated as a “code change”.
“….. The code can be committed after the first +1, unless the code change
represents a merge from a branch, in which case three +1s are required.”
IMO, the only difference between a patch commit and a branch merge is the
requirement of 3 committer +1s.
jitendra
On 4/18/18, 10:34 AM, "Rushabh Shah" <rusha...@oath.com.INVALID> wrote:
Hi All,
Thanks Jitendra for initiating the merge vote.
Just wanted to understand the policy for merge votes.
According to this page: http://hadoop.apache.org/bylaws.html, I assume
merge votes falls under "Adoption of new codebase" and only PMC members
vote are considered binding.
Is my understanding correct ?
On Wed, Apr 18, 2018 at 12:19 PM, Hanisha Koneru <hkon...@hortonworks.com>
wrote:
> +1 (binding)
>
> Thanks,
> Hanisha
>
>
>
>
>
>
>
>
>
> On 4/16/18, 4:48 PM, "Jitendra Pandey" <jiten...@hortonworks.com> wrote:
>
> >Hi All,
> >
> > The community unanimously voted (https://s.apache.org/HDDSMergeResult)
> to adopt
> >HDDS/Ozone as a sub-project of Hadoop, here is the formal vote for code
> merge.
> >
> >Here is a quick summary of the code changes:
> >
> >- As decided in the JIRA HDFS-10419, the project has been renamed to
> Hadoop Distributed Data Store or HDDS.
> >- HDDS becomes a sub-project of Hadoop.
> >- Added a Maven profile that disables HDDS compilation by default.
> >- The releases of HDDS will be independent of Hadoop and will have no
> impact to current Hadoop release process.
> >- We have made HDDS a loadable module.
> >- Cleaned up changes in HDFS/Hadoop Common to make sure HDDS does not
> impact current users of HDFS.
> >
> >The vote will run for 7 days, I will start this vote with my +1.
> >
> >Thanks
> >Jitendra
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> >For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
> >
>
