Re: [VOTE] Migration from subversion to git for version control
Filed https://issues.apache.org/jira/browse/INFRA-8195. I encourage folks to watch the issue and at least some of us help with verifying the migration moves everything. On Sat, Aug 16, 2014 at 8:25 AM, Karthik Kambatla wrote: > Thanks everyone for voting. Here is my +1 (non-binding). > > The vote closes with 27 +1s (15 binding). I ll work with INFRA on the > migration, and draft a wiki for "How To" with git. > > > On Thu, Aug 14, 2014 at 4:34 PM, Jonathan Eagles > wrote: > >> +1 >> On Aug 14, 2014 5:56 PM, "Hitesh Shah" wrote: >> >> > +1 >> > >> > — Hitesh >> > >> > On Aug 8, 2014, at 7: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 >> > > ". >> > > 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. >> > >> > >> > >
Re: [VOTE] Migration from subversion to git for version control
Thanks everyone for voting. Here is my +1 (non-binding). The vote closes with 27 +1s (15 binding). I ll work with INFRA on the migration, and draft a wiki for "How To" with git. On Thu, Aug 14, 2014 at 4:34 PM, Jonathan Eagles wrote: > +1 > On Aug 14, 2014 5:56 PM, "Hitesh Shah" wrote: > > > +1 > > > > — Hitesh > > > > On Aug 8, 2014, at 7: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 > > > ". > > > 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. > > > > >
Re: [VOTE] Migration from subversion to git for version control
+1 On Aug 14, 2014 5:56 PM, "Hitesh Shah" wrote: > +1 > > — Hitesh > > On Aug 8, 2014, at 7: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 > > ". > > 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. > >
Re: [VOTE] Migration from subversion to git for version control
+1 — Hitesh On Aug 8, 2014, at 7: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 > ". > 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.
Re: [VOTE] Migration from subversion to git for version control
+1 sanjay > > On Fri, Aug 8, 2014 at 7: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 >> ". >> 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. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Migration from subversion to git for version control
+1 -C On Fri, Aug 8, 2014 at 7: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 >". >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.
Re: [VOTE] Migration from subversion to git for version control
+1 binding. On Tue, Aug 12, 2014 at 6:08 AM, Thomas Graves < tgra...@yahoo-inc.com.invalid> wrote: > +1 (binding). > > > Tom > > > On Friday, August 8, 2014 9: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 >". >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. > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Migration from subversion to git for version control
+1 (binding). Tom On Friday, August 8, 2014 9: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 ". 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.
Re: [VOTE] Migration from subversion to git for version control
+1 non-binding On Mon, Aug 11, 2014 at 4:16 PM, wrote: > +1 > > > > > > > From: Colin McCabe > Sent: Monday, August 11, 2014 3:40 PM > To: Hadoop Common > Cc: hdfs-...@hadoop.apache.org, yarn-...@hadoop.apache.org, > mapreduce-...@hadoop.apache.org > > > > > > +1. > > best, > Colin > > On Fri, Aug 8, 2014 at 7: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 > >". > >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. > -- Zhijie Shen Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Migration from subversion to git for version control
+1 From: Colin McCabe Sent: Monday, August 11, 2014 3:40 PM To: Hadoop Common Cc: hdfs-...@hadoop.apache.org, yarn-...@hadoop.apache.org, mapreduce-...@hadoop.apache.org +1. best, Colin On Fri, Aug 8, 2014 at 7: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 >". >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.
Re: [VOTE] Migration from subversion to git for version control
+1. best, Colin On Fri, Aug 8, 2014 at 7: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 >". >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.
Re: [VOTE] Migration from subversion to git for version control
+1 On Mon, Aug 11, 2014 at 1:43 PM, Kihwal Lee wrote: > +1 (binding) > > Kihwal > > On 8/8/14, 9: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 > > ". > > 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. > > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Migration from subversion to git for version control
+1 (binding) Kihwal On 8/8/14, 9: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 > ". > 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.
Re: [VOTE] Migration from subversion to git for version control
+1 (binding) Thanks for driving this, Karthik. -- Aaron T. Myers Software Engineer, Cloudera On Fri, Aug 8, 2014 at 7: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 >". >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. >
Re: [VOTE] Migration from subversion to git for version control
+1. Thanks, Junping On Sat, Aug 9, 2014 at 10:57 AM, 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 >". >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. > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Migration from subversion to git for version control
+1(non-binding) Thanks, - Tsuyoshi On Sat, Aug 9, 2014 at 11:57 AM, 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 >". >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
Re: [VOTE] Migration from subversion to git for version control
+1 (binding)
as this gets rolled out, I think we may also want define a branch naming
policy like feature/${JIRA}-text for features, as well as a policy for
deleting retired branches (tag the last commit then rm the branch)...then
we can cull some branches that are in SVN.
-steve
On 9 August 2014 03:57, 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
>".
>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.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
RE: [VOTE] Migration from subversion to git for version control
+1 Regards, Uma -Original Message- From: Karthik Kambatla [mailto:ka...@cloudera.com] Sent: Saturday, August 09, 2014 8:27 AM To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: [VOTE] Migration from subversion to git for version control 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 ". 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.
Re: [VOTE] Migration from subversion to git for version control
+1 (non-binding) On Sat, Aug 9, 2014 at 8:27 AM, 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 >". >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. > -- Thanks Devaraj K
Re: [VOTE] Migration from subversion to git for version control
+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 wrote: +1 (non-binding) On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe 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 ". 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.
Re: [VOTE] Migration from subversion to git for version control
+1 non binding. -M!T On Aug 10, 2014 4:12 PM, Chen He wrote: +1 (non-binding) On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe 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 >> ". >> 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. >> >> >
Re: [VOTE] Migration from subversion to git for version control
+1 (non-binding) On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe 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 >> ". >> 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. >> >> >
Re: [VOTE] Migration from subversion to git for version control
+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 ". 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.
Re: [VOTE] Migration from subversion to git for version control
+1 On Sun, Aug 10, 2014 at 11:12 AM, Alejandro Abdelnur wrote: > +1 > > Alejandro > (phone typing) > > > On Aug 8, 2014, at 19:57, 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 > > ". > > 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. >
Re: [VOTE] Migration from subversion to git for version control
+1 Alejandro (phone typing) > On Aug 8, 2014, at 19:57, 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 > ". > 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.
Re: [VOTE] Migration from subversion to git for version control
+1 (non-binding) On Sat, Aug 9, 2014 at 9:34 AM, Sandy Ryza wrote: > +1 (binding) > > > On Fri, Aug 8, 2014 at 7: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 > >". > >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. > > >
Re: [VOTE] Migration from subversion to git for version control
+1 (binding) On Fri, Aug 8, 2014 at 7: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 >". >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. >
[VOTE] Migration from subversion to git for version control
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 ". 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.
