hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uma Maheswara Rao G <mahesw...@huawei.com>
Subject RE: [VOTE] Maintain a single committer list for the Hadoop project
Date Tue, 28 Aug 2012 05:35:25 GMT
+1 

Make sense.
Committers knows their limits to commit/review the specific part of the code area where they
are familiar in subprojects. So,  no issues in this proposal to make a single list.
IMO, ok to maintain single list, until we plan to make separate releases of each sub project.

Thanks,
Uma
________________________________________
From: Eli Collins [eli@cloudera.com]
Sent: Saturday, August 25, 2012 4:23 AM
To: general@hadoop.apache.org
Subject: Re: [VOTE] Maintain a single committer list for the Hadoop project

On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins <eli@cloudera.com> wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> rights in all current (Common, HDFS, MapReduce, YARN) and future
> Hadoop subprojects. The specific change to the bylaws follows:
>
> Index: main/author/src/documentation/content/xdocs/bylaws.xml
> ===================================================================
> --- main/author/src/documentation/content/xdocs/bylaws.xml      (revision 1376823)
> +++ main/author/src/documentation/content/xdocs/bylaws.xml      (working copy)
> @@ -64,10 +64,9 @@
>     <li> <strong>Committers</strong>
>
>          <p>The project's Committers are responsible for the project's
> -        technical management. Committers have access to a specified
> -        set of subprojects' subversion repositories. Committers on
> -        subprojects may cast binding votes on any technical discussion
> -        regarding that subproject.</p>
> +        technical management. Committers have access to all subproject
> +        subversion repositories. Committers may cast binding votes on
> +        any technical discussion regarding that subproject.</p>
>

Andy Isaacson pointed out that I should replace "that" with "any"
above in "regarding that subproject" to make this more clear.  Here's
the updated diff, same intent.

site $ svn diff
Index: main/author/src/documentation/content/xdocs/bylaws.xml
===================================================================
--- main/author/src/documentation/content/xdocs/bylaws.xml      (revision 1376823)
+++ main/author/src/documentation/content/xdocs/bylaws.xml      (working copy)
@@ -64,10 +64,9 @@
    <li> <strong>Committers</strong>

         <p>The project's Committers are responsible for the project's
-        technical management. Committers have access to a specified
-        set of subprojects' subversion repositories. Committers on
-        subprojects may cast binding votes on any technical discussion
-        regarding that subproject.</p>
+        technical management. Committers have access to all subproject
+        subversion repositories. Committers may cast binding votes on
+        any technical discussion regarding any subproject.</p>
Mime
View raw message