Return-Path: 
 <mapreduce-dev-return-12245-apmail-hadoop-mapreduce-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E6F33115B0
	for <apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org>;
 Mon, 11 Aug 2014 12:53:08 +0000 (UTC)
Received: (qmail 52556 invoked by uid 500); 11 Aug 2014 12:53:03 -0000
Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org
Received: (qmail 52394 invoked by uid 500); 11 Aug 2014 12:53:03 -0000
Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-dev@hadoop.apache.org>
List-Id: <mapreduce-dev.hadoop.apache.org>
Reply-To: mapreduce-dev@hadoop.apache.org
Delivered-To: mailing list mapreduce-dev@hadoop.apache.org
Received: (qmail 52341 invoked by uid 99); 11 Aug 2014 12:53:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Aug 2014 12:53:03 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ozawa.tsuyoshi@gmail.com
 designates 74.125.82.43 as permitted sender)
Received: from [74.125.82.43] (HELO mail-wg0-f43.google.com) (74.125.82.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Aug 2014 12:52:38 +0000
Received: by mail-wg0-f43.google.com with SMTP id l18so8544418wgh.14
        for <multiple recipients>; Mon, 11 Aug 2014 05:52:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=OOBDe3Pt8oX8vbrPTulBV5C+M/OR87mpl0oBksdirWs=;
        b=Vk73XZ7lVi9QSpbaq9l2/EpF0GlJRNl28GCr14qQyiDYxHov1aCU7UQOC8BORjajxh
         cPsPPFTOsAXEwOi+psIvwackrFPwToPh3B2xYVCFRSzzthMVQj85oAwqoNINwTWFHpRg
         1IfHiEV7PhyOSBWiQ5kdOU/7ni2bFQjdhI1WmS0s4iiGXiVkuu4/o6FyDV981I4ty7AW
         LozEkrS+yC8sF+8JRjey08ECYTOIxa71qbeUuYlWBZTMWqEKgD9zP9pfLEg4xKeYgXi/
         nTrDOu/zB+2yl66m1zo+DswNetm16oLptr2ceczvn7bha02QRX9z9G+K3wu9rgEl+CEb
         mJ+g==
MIME-Version: 1.0
X-Received: by 10.194.89.200 with SMTP id bq8mr44615167wjb.52.1407761557393;
 Mon, 11 Aug 2014 05:52:37 -0700 (PDT)
Received: by 10.216.172.66 with HTTP; Mon, 11 Aug 2014 05:52:37 -0700 (PDT)
In-Reply-To: 
 <CALwhT94Y64M9keY25Ry_QOLUSZQT29tJQ95twsoa8xXrcNTxpQ@mail.gmail.com>
References: 
 <CALwhT94Y64M9keY25Ry_QOLUSZQT29tJQ95twsoa8xXrcNTxpQ@mail.gmail.com>
Date: Mon, 11 Aug 2014 21:52:37 +0900
Message-ID: 
 <CAAD07OK05W54Cv6EygdndiDtnSjofAT_ibFPQ_YRYuhA8knQNQ@mail.gmail.com>
Subject: Re: [VOTE] Migration from subversion to git for version control
From: Tsuyoshi OZAWA <ozawa.tsuyoshi@gmail.com>
To: "yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Cc: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Content-Type: text/plain; charset=UTF-8
X-Virus-Checked: Checked by ClamAV on apache.org

+1(non-binding)

Thanks,
- Tsuyoshi

On Sat, Aug 9, 2014 at 11:57 AM, Karthik Kambatla <kasha@cloudera.com> wrote:
> I have put together this proposal based on recent discussion on this topic.
>
> Please vote on the proposal. The vote runs for 7 days.
>
>    1. Migrate from subversion to git for version control.
>    2. Force-push to be disabled on trunk and branch-* branches. Applying
>    changes from any of trunk/branch-* to any of branch-* should be through
>    "git cherry-pick -x".
>    3. Force-push on feature-branches is allowed. Before pulling in a
>    feature, the feature-branch should be rebased on latest trunk and the
>    changes applied to trunk through "git rebase --onto" or "git cherry-pick
>    <commit-range>".
>    4. Every time a feature branch is rebased on trunk, a tag that
>    identifies the state before the rebase needs to be created (e.g.
>    tag_feature_JIRA-2454_2014-08-07_rebase). These tags can be deleted once
>    the feature is pulled into trunk and the tags are no longer useful.
>    5. The relevance/use of tags stay the same after the migration.
>
> Thanks
> Karthik
>
> PS: Per Andrew Wang, this should be a "Adoption of New Codebase" kind of
> vote and will be Lazy 2/3 majority of PMC members.



-- 
- Tsuyoshi