Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CADcMMgEZjWW6H7FWCmTnFbVgC7hFwZTxcTqzS07GQkT9WnfN_w@mail.gmail.com>
References: 
 <CADcMMgGfrz5vf+t+AwitW2JrpPD0n_2DkNwcH8=dTMuSynXr4w@mail.gmail.com>
 <CAEz+yv_85+ZEGa6e1H9LOUDCF1S+1gt+9gM7Gnyy+PXV+rpAmQ@mail.gmail.com>
 <CANZa=GtghX5AsaORYd8HOWEoGx_soeOg5EKz8pdSCov2n31CPw@mail.gmail.com>
 <CADcMMgHHpgrXxb+2XmjzU31fx9jzENfEKz9n5Tp5_8vTpou08w@mail.gmail.com>
 <CAMUu0w-aFk36Jm0prGvZLPar4fxowYDdzYP3h6h633MGB7X4QA@mail.gmail.com>
 <CA+RK=_A0M-uz9oawDnJQOS4gimGdJ4MPiTuhXX=QRcBFW7tdGw@mail.gmail.com>
 <CADcMMgFbpmOu0ND=wssEHrHRt_a2DPWQjWfCs+_VnhY3_qV0yQ@mail.gmail.com>
 <CALte62weCDr3Dz+Zr=fs1UPbDZxeyE=PsDH-GDUXZbiQq8ei=g@mail.gmail.com>
 <CALte62zjOAoB6kjPB+riiW1tUOQbG8cWjexJVN8Fr02xC4SkqA@mail.gmail.com>
 <CADcMMgEZjWW6H7FWCmTnFbVgC7hFwZTxcTqzS07GQkT9WnfN_w@mail.gmail.com>
From: Andrew Purtell <apurtell@apache.org>
Date: Thu, 22 May 2014 09:28:45 -0700
Message-ID: 
 <CA+RK=_BY1Y7+ZJAfP5xDPoHm1wkuRh2sicGJLvNfDxqvS7ehUA@mail.gmail.com>
Subject: Re: ANNOUNCEMENT: Git Migration In Progress (WAS => Re: Git
 Migration)
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e0158ab1ac1d43504f9ff9d7a

--089e0158ab1ac1d43504f9ff9d7a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Infra has closed the migration ticket.

I looked at tags for trunk/master and 0.98, and these look fine.

Unfortunately there are differences between SVN checkouts and Git
checkouts. SVN has changes on trunk/master and 0.98 that did not make it
over to Git looks like.

master/trunk: http://pastebin.com/dQ6SU2Dz

0.98: http://pastebin.com/Pvk3BH4i

0.96: Good!

0.94: Good!

0.89-fb=E2=80=8B: Good!


On Wed, May 21, 2014 at 10:55 PM, Stack <stack@duboce.net> wrote:

> Thanks T.
>
> The trunk test is still running fine.  Checkout local looks good too.  I
> tried a branch.  It seems right too.  Asking about discrepancy in the tag
> listings between the branches up in the INFRA issue.git.  Working on file
> compares of svn and git checkouts....  Will report back.
>
> St.Ack
>
>
> On Wed, May 21, 2014 at 10:02 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>
> > I pointed trunk Jenkins job to git repo and triggered a build.
> >
> > So far the tests are running fine.
> >
> > FYI
> >
> >
> > On Wed, May 21, 2014 at 7:42 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> >
> > > I 'git clone'd master branch.
> > >
> > > Ran mvn package.
> > > Ran some tests.
> > > Checked 'git log'
> > >
> > > Looks Okay.
> > >
> > >
> > > On Wed, May 21, 2014 at 7:23 PM, Stack <stack@duboce.net> wrote:
> > >
> > >> Migration looks done:
> > https://git-wip-us.apache.org/repos/asf?p=3Dhbase.git
> > >>
> > >> Next up is checking if it is all there.  I was going to check later
> this
> > >> evening but if anyone else wants to compare, that'd be grand.
> > >>
> > >> St.Ack
> > >>
> > >>
> > >>
> > >> On Wed, May 21, 2014 at 6:04 PM, Andrew Purtell <apurtell@apache.org=
>
> > >> wrote:
> > >>
> > >> > I also have done trunk first then cherry pick to branches.
> > >> >
> > >> >
> > >> > On Wed, May 21, 2014 at 4:19 PM, Enis S=C3=B6ztutar <enis.soz@gmai=
l.com>
> > >> wrote:
> > >> >
> > >> > > > crew).  On feature branches, lets see.  Squash if messy histor=
y
> > >> (most
> > >> > > > cases?)?
> > >> > > >
> > >> > > >
> > >> > > One immediate example is HBASE-10070 branch. We wanted a smooth
> > >> merge, so
> > >> > > the branch history is clean and every commit traces to a jira
> (with
> > >> > reviews
> > >> > > etc).
> > >> > >
> > >> > > For "official" feature branches which will be pushed to the main
> > >> repo, I
> > >> > > think we should
> > >> > > require a similar thing. If people need a working branch with
> > >> less-clean
> > >> > > history, there is
> > >> > > no need to push that to the asf repo.
> > >> > >
> > >> > >
> > >> > > > The Accumulo doc makes for a good start [1] (ignoring where
> their
> > >> > > branching
> > >> > > > style is different to ours). It is informed by the Kafka
> > >> contributors
> > >> > > > workflow doc, also a good read [2]. When in doubt, do as we've
> > done
> > >> in
> > >> > > the
> > >> > > > past: e.g. adding patch to JIRA for hadoopqa run. Dump dev pai=
ns
> > and
> > >> > > > suggested solutions into this thread. Lets keep this thread
> alive
> > >> with
> > >> > > > issues we run into as a dev team and our (suggested) solutions=
.
> As
> > >> our
> > >> > > > practice diverges from that outline in docs above, lets note a=
nd
> > add
> > >> > doc
> > >> > > > locally?
> > >> > > >
> > >> > >
> > >> > > +1 for a local doc.
> > >> > > I like both of the documents. Kafka does not touch on merge
> between
> > >> > > branches at all. I used to do
> > >> > > commit-to-master than cherry-pick in the other branches (if
> > >> applicable)
> > >> > > otherwise create a different patch and commit approach rather
> > >> > > than merges across release branches. This is more similar to our
> svn
> > >> > model.
> > >> > >
> > >> > > I think for existing release branches, the merge is out of
> question
> > >> (if I
> > >> > > understand this correctly). We always did trunk-first than
> > cherry-pick
> > >> > into
> > >> > > branches approach, while Accumulo suggests that we do earlier
> branch
> > >> > first,
> > >> > > then merge into master. Since I don't have experience on this,
> > >> > > not sure whether that will work for us or not.
> > >> > >
> > >> > >
> > >> > > >
> > >> > > > I need to heads-up our FB brothers and sisters too....
> > >> > > >
> > >> > > > St.Ack
> > >> > > >
> > >> > > > 1. http://accumulo.apache.org/git.html
> > >> > > > 2.
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+re=
view#Patchsubmissionandreview-Simplecontributorworkflow
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > > Perhaps this has some useful formulae:
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> http://git-scm.com/book/en/Customizing-Git-An-Example-Git-Enforced-Policy
> > >> > > > >
> > >> > > > >
> > >> > > > > On Tue, May 20, 2014 at 10:10 PM, Talat Uyarer <
> > talat@uyarer.com>
> > >> > > wrote:
> > >> > > > >
> > >> > > > > > Good news :)
> > >> > > > > > 21 May 2014 08:05 tarihinde "Stack" <stack@duboce.net>
> yazd=C4=B1:
> > >> > > > > >
> > >> > > > > > > SVN has been flipped read-only.  The migration to git ha=
s
> > >> > started.
> > >> > > >  See
> > >> > > > > > > https://issues.apache.org/jira/browse/INFRA-7768
> > >> > > > > > >
> > >> > > > > > > St.Ack
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > On Mon, May 19, 2014 at 3:56 PM, Stack <stack@duboce.net=
>
> > >> wrote:
> > >> > > > > > >
> > >> > > > > > > > On Mon, May 19, 2014 at 1:48 PM, Talat Uyarer <
> > >> > talat@uyarer.com>
> > >> > > > > > wrote:
> > >> > > > > > > >
> > >> > > > > > > >> Hi All,
> > >> > > > > > > >>
> > >> > > > > > > >> I created an issue for our git migrating. [0] We can
> > follow
> > >> > our
> > >> > > > > > > >> migration status. Fyi
> > >> > > > > > > >>
> > >> > > > > > > >
> > >> > > > > > > > Thank you Talat,
> > >> > > > > > > > St.Ack
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Best regards,
> > >> >
> > >> >    - Andy
> > >> >
> > >> > Problems worthy of attack prove their worth by hitting back. - Pie=
t
> > Hein
> > >> > (via Tom White)
> > >> >
> > >>
> > >
> > >
> >
>


--=20
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

--089e0158ab1ac1d43504f9ff9d7a--