Reading [1] a while back made me think of the status of our own bug database.
According to [2] we have 114 open, unassigned bugs in our tracker for Tapestry 5.1 and 5.0 and even 172 when I include those where no version number has been specified. Those bugs are unlikely to get resolved, many of them may even be fixed by changes we did for later versions of Tapestry. I am inclined to bulk close these with a message that the reporter is free to check if the issue still persists with a more recent version of the framework. Thoughts? Uli [1] http://www.joelonsoftware.com/items/2012/07/09.html [2] http://s.apache.org/5bp --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
