What is holding you back exactly? Cutting a release and pushing it to the staging repo for a VOTE used to be a one-liner that could also easily be implemented as a Jenkins job.
Cheers, Uli On Thu, February 25, 2016 12:58, Jochen Kemnade wrote: > Sure, I do that on Github, but in ASF projects, a little more effort is > required for every release. I'd like to avoid having to create a release > just because changes came in shortly after the last one. That's why I'm > asking if anything else is going to be fixed shortly. > > Jochen > > Ulrich Stärk <u...@spielviel.de> schrieb am Do., 25. Feb. 2016 um 12:28 > Uhr: > >> Release early, release often. 5.4.1 asap, followed by 5.4.2 if more bugs >> get fixed. >> >> Cheers, >> >> Uli >> >> On 24/02/16 15:32, Jochen Kemnade wrote: >> > Hi, >> > >> > the 5.4.0 release was 2 months ago and we have fixed some issues since >> then, some of them bugs: >> > >> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.4.1%20AND%20project%20%3D%20TAP5 >> > >> > Do we want to create a follow-up release anytime soon or should we >> squash some more bugs first? >> > Are there issues currently being worked on that could go into the >> release? >> > What are your plans for 5.4.x? >> > >> > Jochen >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> > For additional commands, e-mail: dev-h...@tapestry.apache.org >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: dev-h...@tapestry.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
