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. >
