I'm fixing what bugs I can. The other committers need to do the same. If we set the bar at "all JIRA issues closed", we'd never be able to create a release, short of arbitrarily closing large swaths of bugs.
Providing patches *with tests* is a good way to get your bugs fixed in 5.3. It sounds harsh, but from my perspective: - Tapestry 5.3 does everything I (and my clients) need it to do - Every hour fixing Tapestry bugs is an hour less consulting (and earning income) for me On Mon, Oct 17, 2011 at 11:53 AM, Lenny Primak <[email protected]> wrote: > Does this include the outstanding jira issues that are around? > Thanks > > > On Oct 17, 2011, at 2:49 PM, Howard Lewis Ship <[email protected]> wrote: > >> I'm pushing to get the last few important bugs fixed before switching >> over to a release candidate. >> >> Once in RC, only blocking bugs will be fixed. >> >> I hope we can get an RC out there and give it a few weeks for people >> to adopt and report back before progressing to the final release vote. >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
