You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by Karthik Kambatla <ka...@cloudera.com> on 2014/08/09 04:57:00 UTC
[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
<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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Sangjin Lee <sj...@gmail.com>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 9:34 AM, Sandy Ryza <sa...@cloudera.com> wrote:
> +1 (binding)
>
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Sangjin Lee <sj...@gmail.com>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 9:34 AM, Sandy Ryza <sa...@cloudera.com> wrote:
> +1 (binding)
>
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Sangjin Lee <sj...@gmail.com>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 9:34 AM, Sandy Ryza <sa...@cloudera.com> wrote:
> +1 (binding)
>
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Sangjin Lee <sj...@gmail.com>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 9:34 AM, Sandy Ryza <sa...@cloudera.com> wrote:
> +1 (binding)
>
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Sandy Ryza <sa...@cloudera.com>.
+1 (binding)
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Brandon Li <br...@hortonworks.com>.
+1
On Mon, Aug 11, 2014 at 1:43 PM, Kihwal Lee <ki...@yahoo-inc.com.invalid>
wrote:
> +1 (binding)
>
> Kihwal
>
> On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
>
>
--
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
Posted by Brandon Li <br...@hortonworks.com>.
+1
On Mon, Aug 11, 2014 at 1:43 PM, Kihwal Lee <ki...@yahoo-inc.com.invalid>
wrote:
> +1 (binding)
>
> Kihwal
>
> On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
>
>
--
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
Posted by Brandon Li <br...@hortonworks.com>.
+1
On Mon, Aug 11, 2014 at 1:43 PM, Kihwal Lee <ki...@yahoo-inc.com.invalid>
wrote:
> +1 (binding)
>
> Kihwal
>
> On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
>
>
--
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
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)
Kihwal
On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Andrew Wang <an...@cloudera.com>.
+1
On Sun, Aug 10, 2014 at 11:12 AM, Alejandro Abdelnur <tu...@cloudera.com>
wrote:
> +1
>
> Alejandro
> (phone typing)
>
> > On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Andrew Wang <an...@cloudera.com>.
+1
On Sun, Aug 10, 2014 at 11:12 AM, Alejandro Abdelnur <tu...@cloudera.com>
wrote:
> +1
>
> Alejandro
> (phone typing)
>
> > On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Andrew Wang <an...@cloudera.com>.
+1
On Sun, Aug 10, 2014 at 11:12 AM, Alejandro Abdelnur <tu...@cloudera.com>
wrote:
> +1
>
> Alejandro
> (phone typing)
>
> > On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Andrew Wang <an...@cloudera.com>.
+1
On Sun, Aug 10, 2014 at 11:12 AM, Alejandro Abdelnur <tu...@cloudera.com>
wrote:
> +1
>
> Alejandro
> (phone typing)
>
> > On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
Alejandro
(phone typing)
> On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Vinayakumar B <vi...@apache.org>.
+1 non-binding
Once this movement is done, detailed steps to checkout, commit and merge
to/from different branches needs to be updated.
Many (including me ;) ) might not know some advanced commands.
Regards,
Vinay
On Tue, Aug 12, 2014 at 5:08 AM, Zhijie Shen <zs...@hortonworks.com> wrote:
> +1 non-binding
>
>
> On Mon, Aug 11, 2014 at 4:16 PM, <jg...@gmail.com> wrote:
>
> > +1
> >
> >
> >
> >
> >
> >
> > From: Colin McCabe
> > Sent: Monday, August 11, 2014 3:40 PM
> > To: Hadoop Common
> > Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org,
> > mapreduce-dev@hadoop.apache.org
> >
> >
> >
> >
> >
> > +1.
> >
> > best,
> > Colin
> >
> > On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
> >
>
>
>
> --
> 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
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1 non-binding
On Mon, Aug 11, 2014 at 4:16 PM, <jg...@gmail.com> wrote:
> +1
>
>
>
>
>
>
> From: Colin McCabe
> Sent: Monday, August 11, 2014 3:40 PM
> To: Hadoop Common
> Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org,
> mapreduce-dev@hadoop.apache.org
>
>
>
>
>
> +1.
>
> best,
> Colin
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1 non-binding
On Mon, Aug 11, 2014 at 4:16 PM, <jg...@gmail.com> wrote:
> +1
>
>
>
>
>
>
> From: Colin McCabe
> Sent: Monday, August 11, 2014 3:40 PM
> To: Hadoop Common
> Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org,
> mapreduce-dev@hadoop.apache.org
>
>
>
>
>
> +1.
>
> best,
> Colin
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1 non-binding
On Mon, Aug 11, 2014 at 4:16 PM, <jg...@gmail.com> wrote:
> +1
>
>
>
>
>
>
> From: Colin McCabe
> Sent: Monday, August 11, 2014 3:40 PM
> To: Hadoop Common
> Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org,
> mapreduce-dev@hadoop.apache.org
>
>
>
>
>
> +1.
>
> best,
> Colin
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1 non-binding
On Mon, Aug 11, 2014 at 4:16 PM, <jg...@gmail.com> wrote:
> +1
>
>
>
>
>
>
> From: Colin McCabe
> Sent: Monday, August 11, 2014 3:40 PM
> To: Hadoop Common
> Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org,
> mapreduce-dev@hadoop.apache.org
>
>
>
>
>
> +1.
>
> best,
> Colin
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by jg...@gmail.com.
+1
From: Colin McCabe
Sent: Monday, August 11, 2014 3:40 PM
To: Hadoop Common
Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by jg...@gmail.com.
+1
From: Colin McCabe
Sent: Monday, August 11, 2014 3:40 PM
To: Hadoop Common
Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by jg...@gmail.com.
+1
From: Colin McCabe
Sent: Monday, August 11, 2014 3:40 PM
To: Hadoop Common
Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by jg...@gmail.com.
+1
From: Colin McCabe
Sent: Monday, August 11, 2014 3:40 PM
To: Hadoop Common
Cc: hdfs-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Colin McCabe <cm...@alumni.cmu.edu>.
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Steve Loughran <st...@hortonworks.com>.
+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 <ka...@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.
>
--
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
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
Alejandro
(phone typing)
> On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Steve Loughran <st...@hortonworks.com>.
+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 <ka...@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.
>
--
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
Posted by Steve Loughran <st...@hortonworks.com>.
+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 <ka...@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.
>
--
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
Posted by Colin McCabe <cm...@alumni.cmu.edu>.
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1 binding.
On Tue, Aug 12, 2014 at 6:08 AM, Thomas Graves <
tgraves@yahoo-inc.com.invalid> wrote:
> +1 (binding).
>
>
> Tom
>
>
> On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1 binding.
On Tue, Aug 12, 2014 at 6:08 AM, Thomas Graves <
tgraves@yahoo-inc.com.invalid> wrote:
> +1 (binding).
>
>
> Tom
>
>
> On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1 binding.
On Tue, Aug 12, 2014 at 6:08 AM, Thomas Graves <
tgraves@yahoo-inc.com.invalid> wrote:
> +1 (binding).
>
>
> Tom
>
>
> On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1 binding.
On Tue, Aug 12, 2014 at 6:08 AM, Thomas Graves <
tgraves@yahoo-inc.com.invalid> wrote:
> +1 (binding).
>
>
> Tom
>
>
> On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Thomas Graves <tg...@yahoo-inc.com.INVALID>.
+1 (binding).
Tom
On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)
Kihwal
On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+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 <ai...@gmail.com> wrote:
> +1 (non-binding)
>
>
>
>
> On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jl...@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.
>>>
>>>
>>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+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 <ai...@gmail.com> wrote:
> +1 (non-binding)
>
>
>
>
> On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jl...@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.
>>>
>>>
>>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+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 <ai...@gmail.com> wrote:
> +1 (non-binding)
>
>
>
>
> On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jl...@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.
>>>
>>>
>>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+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 <ai...@gmail.com> wrote:
> +1 (non-binding)
>
>
>
>
> On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jl...@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.
>>>
>>>
>>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Mit Desai <mi...@yahoo-inc.com.INVALID>.
+1 non binding.
-M!T
On Aug 10, 2014 4:12 PM, Chen He <ai...@gmail.com> wrote:
+1 (non-binding)
On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jl...@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.
>>
>>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Chen He <ai...@gmail.com>.
+1 (non-binding)
On Sun, Aug 10, 2014 at 3:44 PM, Jason Lowe <jl...@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.
>>
>>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Junping Du <jd...@hortonworks.com>.
+1.
Thanks,
Junping
On Sat, Aug 9, 2014 at 10:57 AM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Junping Du <jd...@hortonworks.com>.
+1.
Thanks,
Junping
On Sat, Aug 9, 2014 at 10:57 AM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Junping Du <jd...@hortonworks.com>.
+1.
Thanks,
Junping
On Sat, Aug 9, 2014 at 10:57 AM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Junping Du <jd...@hortonworks.com>.
+1.
Thanks,
Junping
On Sat, Aug 9, 2014 at 10:57 AM, Karthik Kambatla <ka...@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.
>
--
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
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1(non-binding)
Thanks,
- Tsuyoshi
On Sat, Aug 9, 2014 at 11:57 AM, Karthik Kambatla <ka...@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
Re: [VOTE] Migration from subversion to git for version control
Posted by Steve Loughran <st...@hortonworks.com>.
+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 <ka...@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.
>
--
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
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <ka...@cloudera.com>
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 <je...@gmail.com>
> wrote:
>
>> +1
>> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>>
>> > +1
>> >
>> > — Hitesh
>> >
>> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>> >
>> >
>>
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <ka...@cloudera.com>
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 <je...@gmail.com>
> wrote:
>
>> +1
>> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>>
>> > +1
>> >
>> > — Hitesh
>> >
>> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>> >
>> >
>>
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <ka...@cloudera.com>
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 <je...@gmail.com>
> wrote:
>
>> +1
>> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>>
>> > +1
>> >
>> > — Hitesh
>> >
>> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>> >
>> >
>>
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <ka...@cloudera.com>
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 <je...@gmail.com>
> wrote:
>
>> +1
>> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>>
>> > +1
>> >
>> > — Hitesh
>> >
>> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>> >
>> >
>>
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <je...@gmail.com> wrote:
> +1
> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>
> > +1
> >
> > — Hitesh
> >
> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
> >
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <je...@gmail.com> wrote:
> +1
> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>
> > +1
> >
> > — Hitesh
> >
> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
> >
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <je...@gmail.com> wrote:
> +1
> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>
> > +1
> >
> > — Hitesh
> >
> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
> >
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Karthik Kambatla <ka...@cloudera.com>.
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 <je...@gmail.com> wrote:
> +1
> On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
>
> > +1
> >
> > — Hitesh
> >
> > On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
> >
> >
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Jonathan Eagles <je...@gmail.com>.
+1
On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
> +1
>
> — Hitesh
>
> On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Jonathan Eagles <je...@gmail.com>.
+1
On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
> +1
>
> — Hitesh
>
> On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Jonathan Eagles <je...@gmail.com>.
+1
On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
> +1
>
> — Hitesh
>
> On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Jonathan Eagles <je...@gmail.com>.
+1
On Aug 14, 2014 5:56 PM, "Hitesh Shah" <hi...@apache.org> wrote:
> +1
>
> — Hitesh
>
> On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
>
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Hitesh Shah <hi...@apache.org>.
+1
— Hitesh
On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+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.
>
RE: [VOTE] Migration from subversion to git for version control
Posted by "Gangumalla, Uma" <um...@intel.com>.
+1
Regards,
Uma
-----Original Message-----
From: Karthik Kambatla [mailto:kasha@cloudera.com]
Sent: Saturday, August 09, 2014 8:27 AM
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@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
<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.
Re: [VOTE] Migration from subversion to git for version control
Posted by sanjay Radia <sa...@hortonworks.com>.
+1
sanjay
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
--
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
Posted by sanjay Radia <sa...@hortonworks.com>.
+1
sanjay
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
--
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
Posted by sanjay Radia <sa...@hortonworks.com>.
+1
sanjay
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
--
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
Posted by sanjay Radia <sa...@hortonworks.com>.
+1
sanjay
>
> On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
--
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
Posted by Chris Douglas <cd...@apache.org>.
+1 -C
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by "Aaron T. Myers" <at...@cloudera.com>.
+1 (binding)
Thanks for driving this, Karthik.
--
Aaron T. Myers
Software Engineer, Cloudera
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by "Aaron T. Myers" <at...@cloudera.com>.
+1 (binding)
Thanks for driving this, Karthik.
--
Aaron T. Myers
Software Engineer, Cloudera
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Devaraj K <de...@apache.org>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 8:27 AM, Karthik Kambatla <ka...@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.
>
--
Thanks
Devaraj K
RE: [VOTE] Migration from subversion to git for version control
Posted by "Gangumalla, Uma" <um...@intel.com>.
+1
Regards,
Uma
-----Original Message-----
From: Karthik Kambatla [mailto:kasha@cloudera.com]
Sent: Saturday, August 09, 2014 8:27 AM
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@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
<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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1(non-binding)
Thanks,
- Tsuyoshi
On Sat, Aug 9, 2014 at 11:57 AM, Karthik Kambatla <ka...@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
Re: [VOTE] Migration from subversion to git for version control
Posted by Chris Douglas <cd...@apache.org>.
+1 -C
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Hitesh Shah <hi...@apache.org>.
+1
— Hitesh
On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)
Kihwal
On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Colin McCabe <cm...@alumni.cmu.edu>.
+1.
best,
Colin
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Hitesh Shah <hi...@apache.org>.
+1
— Hitesh
On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Thomas Graves <tg...@yahoo-inc.com.INVALID>.
+1 (binding).
Tom
On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Sandy Ryza <sa...@cloudera.com>.
+1 (binding)
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Chris Douglas <cd...@apache.org>.
+1 -C
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Devaraj K <de...@apache.org>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 8:27 AM, Karthik Kambatla <ka...@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.
>
--
Thanks
Devaraj K
Re: [VOTE] Migration from subversion to git for version control
Posted by Sandy Ryza <sa...@cloudera.com>.
+1 (binding)
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Hitesh Shah <hi...@apache.org>.
+1
— Hitesh
On Aug 8, 2014, at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Devaraj K <de...@apache.org>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 8:27 AM, Karthik Kambatla <ka...@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.
>
--
Thanks
Devaraj K
Re: [VOTE] Migration from subversion to git for version control
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
Alejandro
(phone typing)
> On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by "Aaron T. Myers" <at...@cloudera.com>.
+1 (binding)
Thanks for driving this, Karthik.
--
Aaron T. Myers
Software Engineer, Cloudera
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)
Kihwal
On 8/8/14, 9:57 PM, "Karthik Kambatla" <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
Alejandro
(phone typing)
> On Aug 8, 2014, at 19:57, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Thomas Graves <tg...@yahoo-inc.com.INVALID>.
+1 (binding).
Tom
On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by "Aaron T. Myers" <at...@cloudera.com>.
+1 (binding)
Thanks for driving this, Karthik.
--
Aaron T. Myers
Software Engineer, Cloudera
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
>
Re: [VOTE] Migration from subversion to git for version control
Posted by Chris Douglas <cd...@apache.org>.
+1 -C
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla <ka...@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.
Re: [VOTE] Migration from subversion to git for version control
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1(non-binding)
Thanks,
- Tsuyoshi
On Sat, Aug 9, 2014 at 11:57 AM, Karthik Kambatla <ka...@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
Re: [VOTE] Migration from subversion to git for version control
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1(non-binding)
Thanks,
- Tsuyoshi
On Sat, Aug 9, 2014 at 11:57 AM, Karthik Kambatla <ka...@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
Re: [VOTE] Migration from subversion to git for version control
Posted by Devaraj K <de...@apache.org>.
+1 (non-binding)
On Sat, Aug 9, 2014 at 8:27 AM, Karthik Kambatla <ka...@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.
>
--
Thanks
Devaraj K
Re: [VOTE] Migration from subversion to git for version control
Posted by Thomas Graves <tg...@yahoo-inc.com.INVALID>.
+1 (binding).
Tom
On Friday, August 8, 2014 9:57 PM, Karthik Kambatla <ka...@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.