Validating the release by following quickstarts being a manual process I believe is still the largest pain point: * We missed that the archetypes were missing the mobile gaming examples. * The tcnative dependency conflict that we needed to cut RC2 for.
Overall much smoother then the prior release but still a good amount of manual steps involved. On Tue, Feb 27, 2018 at 9:16 AM, Reuven Lax <re...@google.com> wrote: > Thanks for fixing the manual cleanup issue! This is something we kept > punting on in previous releases. > > > On Mon, Feb 26, 2018 at 7:14 PM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> Hi Alan, >> >> Honestly, it was an easy and smooth release, similar to other Apache >> project >> release. >> >> Maybe the points where we could a little bit improve are: >> >> 1. The website update was pretty long as @asfgit merge didn't work (due >> to a out >> of sync on the github mirror). I think the website publish PR can be >> automatized. >> 2. Upload to pylib required manual action (like renaming the files) >> >> Thanks to the change I did on the assembly, the artifacts don't require >> any >> manual cleanup (whereas it was the case in previous release). >> >> Regards >> JB >> >> On 02/26/2018 10:54 PM, Alan Myrvold wrote: >> > Is there a list of pain points during the 2.3.0 release and >> improvements that >> > can be made to the 2.4.0 release process? >> > >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> >
