In the bylaws, I see this under PMC responsibilities:
* Maintaining the project's shared resources, including the codebase
repository, mailing lists, websites.
This seems to indicate that the repo (i.e. svn or git) is managed by the
PMC. Of the available PMC vote actions, the closest seems to be
funny, i'd treat it as a merge vote.
On Fri, Aug 8, 2014 at 11:44 AM, Karthik Kambatla
wrote:
> Thanks Steve. Including that in the proposal.
>
> By the way, from our project bylaws (http://hadoop.apache.org/bylaws.html
> ),
> I can't tell what kind of a vote this would be.
>
>
> On Thu, Aug 7,
Thanks Steve. Including that in the proposal.
By the way, from our project bylaws (http://hadoop.apache.org/bylaws.html),
I can't tell what kind of a vote this would be.
On Thu, Aug 7, 2014 at 1:22 AM, Steve Loughran
wrote:
> On 6 August 2014 22:16, Karthik Kambatla wrote:
>
> > 3. Force-push
I plan to propose the following in the vote thread. Please advise on more
details to be added and/or concerns you have so we avoid the overhead of
doing this in the vote thread.
1. Migrate from subversion to git for version control
2. Force-push to be disabled on trunk and branch-* branches. Apply
By "merge-based workflow", this is referring to branch development and
merging? I don't see much issue with allowing a rebase-based workflow if
we're okay with allowing force-push on feature branches. If anything, the
next step would be disallowing merge-based workflows and mandating rebases
for a
If by very same workflow you mean a merge-based workflow that would be fine
to call out in the vote proposal.
Separately, do we want to disable force push for version branches
(branch-x) and point release branches (branch-x.y) in addition to trunk?
On Tue, Aug 5, 2014 at 8:18 PM, Alejandro Abdel
I would say we can first move to git and keep the very same workflow we
have today, then we can evolve it.
On Tue, Aug 5, 2014 at 6:46 PM, Arpit Agarwal
wrote:
> +1 to voting on specific workflow(s).
>
>
> On Tue, Aug 5, 2014 at 5:49 PM, Karthik Kambatla
> wrote:
>
> > If we are to start a vot
+1 to voting on specific workflow(s).
On Tue, Aug 5, 2014 at 5:49 PM, Karthik Kambatla wrote:
> If we are to start a vote thread, will people prefer a vote thread that
> includes potential workflows as well?
>
>
> On Tue, Aug 5, 2014 at 5:40 PM, Karthik Kambatla
> wrote:
>
> > Thanks for your
If we are to start a vote thread, will people prefer a vote thread that
includes potential workflows as well?
On Tue, Aug 5, 2014 at 5:40 PM, Karthik Kambatla wrote:
> Thanks for your opinions, everyone. Looks like most people are for the
> change and no one is against it. Let me start a vote f
Thanks for your opinions, everyone. Looks like most people are for the
change and no one is against it. Let me start a vote for this.
On Mon, Aug 4, 2014 at 4:44 PM, Tsuyoshi OZAWA
wrote:
> Thank you for supplementation, Andrew. Yes, we should go step by step
> and let's discuss review workflow
Thank you for supplementation, Andrew. Yes, we should go step by step
and let's discuss review workflows on a another thread.
Thanks,
- Tsuyoshi
On Tue, Aug 5, 2014 at 8:23 AM, Andrew Wang wrote:
> I think we should take things one step at a time. Switching to git
> definitely opens up the possi
I think we should take things one step at a time. Switching to git
definitely opens up the possibility for better review workflows, but we can
discuss that on a different thread.
A few different people have also mentioned Gerrit, so that'd be in the
running along with Github (and I guess ReviewBoa
Thank you for great suggestion, Karthik. +1(non-binding) to use git.
I'm also using private git repository.
Additionally, I have one question. Will we accept github-based
development like Apache Spark? IHMO, it allow us to leverage Hadoop
development, because the cost of sending pull request is ver
+1, Git is more convenient for development and we can switch easily between
branches and can have local branches.
Regards,
Yi Liu
-Original Message-
From: Karthik Kambatla [mailto:ka...@cloudera.com]
Sent: Saturday, August 02, 2014 7:44 AM
To: common-...@hadoop.apache.org; hdfs-dev@had
+1 for this =)
Been using Github mirror for development anyway =)
We at Apache Gora moved to Git recently and it had been pretty smooth
transition.
- Henry
On Fri, Aug 1, 2014 at 4:43 PM, Karthik Kambatla wrote:
> Hi folks,
>
> From what I hear, a lot of devs use the git mirror for development
+1, we did it for Oozie a while back and was painless with minor issues in
Jenkins jobs
Rebasing feature branches on latest trunk may be tricky as that may require
a force push and if I'm not mistaken force pushes are disabled in Apache
GIT.
thx
On Fri, Aug 1, 2014 at 4:43 PM, Karthik Kambatla
Thanks for starting this thread Karthik! Big +1 from me. I only use svn
when I have to commit things or work on the site, otherwise it's always the
git mirror or local git repos.
Considering that the git mirror works as well as it does, I'd expect this
to be a pretty smooth transition.
Best,
Andr
17 matches
Mail list logo
