Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 andrew.bayer@gmail.com does not designate 54.76.25.247 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ2HCd8M3fnFD8akWM4wXR9myT7DGoKkQvqsFgXOz+nuD3HoGA@mail.gmail.com>
References: <1429345996.2703.19.camel@winder.org.uk>
	<CAJ2HCd-Ka0+mUf=b27s+bnkNAWL=QgVaDtznkEqvaE_NDBB62Q@mail.gmail.com>
	<1429373705.31282.12.camel@winder.org.uk>
	<5532922C.4000800@gmx.net>
	<55329371.60408@gmx.net>
	<1429448854.3327.4.camel@winder.org.uk>
	<5533FEC1.5070502@gmx.org>
	<CAJ2HCd8M3fnFD8akWM4wXR9myT7DGoKkQvqsFgXOz+nuD3HoGA@mail.gmail.com>
Date: Sun, 19 Apr 2015 12:54:13 -0700
Message-ID: 
 <CAPbPdOYqiYgvMR_8Ty93vps2VP0WaFsVHeVy-eUmvtUFdnEUCQ@mail.gmail.com>
Subject: =?UTF-8?Q?Re=3A_New_Workflow=E2=80=A6?=
From: Andrew Bayer <andrew.bayer@gmail.com>
To: dev@groovy.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c383ce7b7a5b0514192d75

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

I'm working on getting Gerrit going here. Until then, all commits must be
made to the ASF repo - we have legal requirements around traceability, push
logs, etc that, as of now, GitHub can't satisfy, so all ASF projects are
required to push all commits directly to the ASF-hosted repositories.

A.
On Apr 19, 2015 12:42, "Guillaume Laforge" <glaforge@gmail.com> wrote:

> But that's what Russel would like :-)
>
> 2015-04-19 21:15 GMT+02:00 Jochen Theodorou <blackdrag@gmx.org>:
>
> > Am 19.04.2015 15:07, schrieb Russel Winder:
> >
> >> On Sat, 2015-04-18 at 19:25 +0200, Pascal Schumacher wrote:
> >>
> >>> [=E2=80=A6]
> >>>
> >>>>
> >>>> We just have to merge pull request by hand into our local copy of
> >>>> the
> >>>> apache repository and then push to the apache repo. From there the
> >>>> changes will be mirrored to github.
> >>>>
> >>>
> >>> So for non-commiters the workflow is the same as before. Just the
> >>> person
> >>> merging the pull request has to do bit more work.
> >>>
> >>
> >> This seems, well, insane. Why can't the merging all happen on GitHub,
> >> with the Apache mainline actually being a mirror of the GitHub one,
> >> even though the Apache mainline is the official definition of the
> >> project.
> >>
> >
> > I think there is a small mistake. The Github repo is a mirror of the
> > apache one, not the other way around. So if you merged on github, you
> would
> > merge on the mirror.
> >
> > bye blackdrag
> >
> > --
> > Jochen "blackdrag" Theodorou
> > blog: http://blackdragsview.blogspot.com/
> >
> >
>
>
> --
> Guillaume Laforge
> Groovy Project Manager
> Product Ninja & Advocate at Restlet <http://restlet.com>
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge <http://twitter.com/glaforge> / Google+
> <https://plus.google.com/u/0/114130972232398734985/posts>
>

--001a11c383ce7b7a5b0514192d75--