I don't know but it doesn't appear in https://issues.apache.org/jira/browse/INFRA-9338. Meanwhile, I uploaded it to our server [1]. Would the wiki let us work on adoc? Also you might find this blog post [2] useful.
[1] http://groovy-lang.org/internal/groovy-release.html [2] http://blog.jetbrains.com/teamcity/2015/01/how-groovy-uses-teamcity/ 2015-03-26 21:08 GMT+01:00 Andrew Bayer <[email protected]>: > Yup, Apache mailing lists don't like attachments. =) > > 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édric Champeau < > [email protected] > > 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 > about > > our builds and what we do, I think it would be good if we could > collaborate > > 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 <[email protected]>: > > > >> 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 > to > >> know what requirements, environments, etc Groovy has now, as well as > what > >> 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 > work > >> on this stuff, so, yeah. =) > >> > >> A. > >> > > > > >
