Two things: if it isn't fixed, it shouldn't have a fix release. If it has a fix release, it may show up in the release notes incorrectly.
Second, I was picturing this purge as being more about invalid or non-reproducible bugs. This improvement request, for example, is valid (just very low priority). ---------- Forwarded message ---------- From: Massimo Lusetti (JIRA) <[email protected]> Date: Thu, Aug 11, 2011 at 3:20 PM Subject: [jira] [Closed] (TAP5-199) Tapestry writes localization initialization information for DateField even when in locale "en" To: [email protected] [ https://issues.apache.org/jira/browse/TAP5-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-199. -------------------------------- Resolution: Won't Fix Fix Version/s: 5.3 Please open a new one for 5.3 if this still applicable > Tapestry writes localization initialization information for DateField even > when in locale "en" > ---------------------------------------------------------------------------------------------- > > Key: TAP5-199 > URL: https://issues.apache.org/jira/browse/TAP5-199 > Project: Tapestry 5 > Issue Type: Improvement > Affects Versions: 5.0.15 > Reporter: Howard M. Lewis Ship > Priority: Minor > Fix For: 5.3 > > > This is an optimization; the client-side DatePicker starts configured for > locale "en" and only needs localization initialization for other locales. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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]
