me, April 3rd, "Re: Update of headers" > I have updated the license on master and 2.4.x. I think updating 2.3 should be only necessary if we ever release this maintenance branch again. If you guys have some time to check at least master, would be nice (so that we don't discover problems too late, during a release...).
Paul King, May 31st, "Re: In shape for a 2.4.4 release" > It might also be nice if one of our mentors can do a trial run check of the source dist zip for us. You can find snapshot artifacts similar to what we would produce for the release on the CI server: > http://ci.groovy-lang.org/viewLog.html?buildId=23085&tab=artifacts&buildTypeId=Groovy_Jdk7Build <http://ci.groovy-lang.org/viewLog.html?buildId=23085&tab=artifacts&buildTypeId=Groovy_Jdk7Build> > [build number will vary - you might need to traverse down from a higher directory - click on "artifacts" on the "JDK 7 Build"] We cannot say it wasn't asked, we did. I understand it wasn't done, everybody has a life, but you can't say we didn't ask :) 2015-06-08 11:33 GMT+02:00 Emmanuel Lécharny <elecha...@gmail.com>: > Le 08/06/15 11:15, Jochen Theodorou a écrit : > > Am 08.06.2015 11:07, schrieb Emmanuel Lécharny: > > [...] > >>> Our build always produces those artifacts so > >>> it was easy to check. > >> We don't check the packages regularly. The idea is to have a process > >> that do that *before* the release, in order to cacth all of the issues. > >> But there is more than just the packages, and it would have been > >> convenient to ask for a pre-check before the release to avoid such > >> frustrating problem. > > > > he did ask afaik > I re-read all the mails, but can't find where it was asked for. > >
