hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Akira AJISAKA <ajisa...@oss.nttdata.co.jp>
Subject Re: [VOTE] Migration from subversion to git for version control
Date Mon, 11 Aug 2014 06:21:35 GMT
+1 (non-binding), I don't use subversion at all in creating patches.
After the migration, we need to change test-patch.sh to use git.

Thanks,
Akira

(2014/08/11 7:18), Mit Desai wrote:
> +1 non binding.
>
> -M!T
>
> On Aug 10, 2014 4:12 PM, Chen He <airbots@gmail.com> wrote:
> +1 (non-binding)
>
>
>
>
> On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jlowe@yahoo-inc.com.invalid>
> wrote:
>
>> +1
>>
>> Jason
>>
>>
>> On 08/08/2014 09:57 PM, Karthik Kambatla 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.
>>>
>>>
>>
>


Mime
View raw message