Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of andrew.bayer@gmail.com
 designates 74.125.82.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADQzvmnbzeX8LH6OTELowMnjzz17mmpjU10hkydzr8+xUdhHHg@mail.gmail.com>
References: 
 <CAPbPdObsS-6G20-wB02huW4r2b+xH_108SZFmyd2z_7X93E-Dw@mail.gmail.com>
 <CADQzvmnbzeX8LH6OTELowMnjzz17mmpjU10hkydzr8+xUdhHHg@mail.gmail.com>
From: Andrew Bayer <andrew.bayer@gmail.com>
Date: Thu, 26 Mar 2015 13:08:52 -0700
Message-ID: 
 <CAPbPdOaYQjA_WfFfBfyQ3heAvsdj=jYnq9mZra71Fcd0647yNQ@mail.gmail.com>
Subject: Re: Build/CI infrastructure etc
To: dev@groovy.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c2270cebbd1a0512369647

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

Yup, Apache mailing lists don't like attachments. =3D)

Did we get a JIRA opened for a wiki space? That would seem to be the
logical place to put the doc...

A.

On Thu, Mar 26, 2015 at 12:49 PM, C=C3=A9dric Champeau <cedric.champeau@gma=
il.com
> wrote:

> Hi Andrew,
>
> This is exactly why I was excited to have you on board as a mentor :) I
> have actually started writing a document (in asciidoctor) that I have
> attached (unless the ML doesn't allow attachments) which describes our
> release process and how TeamCity comes in action. It contains details abo=
ut
> our builds and what we do, I think it would be good if we could collabora=
te
> on this doc, even if I have no strong opinion about where it should sit
> (apart that it should not belong to the codebase);
>
> 2015-03-26 20:36 GMT+01:00 Andrew Bayer <andrew.bayer@gmail.com>:
>
>> Since this is my particular area (both professionally and here at ASF
>> Infra), I thought I'd start a discussion on what Groovy has now, what
>> Groovy needs going forward, and how to get there. I know Groovy's got a
>> bunch of things going on TeamCity currently - so long as whoever's
>> providing those resources is willing to keep doing so, that can continue=
.
>> There's no reason we have to suddenly turn it off just because we're at
>> Apache now.
>>
>> Buuuuuut I want to do awesome things with builds.apache.org. So I want t=
o
>> know what requirements, environments, etc Groovy has now, as well as wha=
t
>> we'd like going forward, so that I can find a way to meet those needs on
>> ASF infra in the future. I'm literally always looking for excuses to wor=
k
>> on this stuff, so, yeah. =3D)
>>
>> A.
>>
>
>

--001a11c2270cebbd1a0512369647--