On Thu, Aug 11, 2011 at 5:44 PM, Josh Canfield <[email protected]> wrote: >> Thanks for stepping forward and volunteering, Josh! > Of course. I like to help out where I can ;) > >> This isn't just blanket closing of issues, but if the issue is obscure >> and not well described, I think it is valid to add a polite message >> asking for it to be reopened when a test case is made available > > Sure. The two issues that got emailed back to me didn't look like they > had any due diligence performed. > > TAP5-178 - Support for optional validator constraints > As far as I know this is still a valid request. > > TAP5-31 - DateField Calendar component has scroll bar burn through > Has the calendar implementation changed?
I agree ... those still feel valid to me as well. > > They just have been closed with a "Please open a new one for 5.3 if > this still applicable" > > Josh > > On Thu, Aug 11, 2011 at 4:37 PM, Howard Lewis Ship <[email protected]> wrote: >> On Thu, Aug 11, 2011 at 3:50 PM, Josh Canfield <[email protected]> >> wrote: >>> I have a problem with closing defects as "Might not be a problem >>> anymore". Do at least some due diligence so you can at least say >>> "can't reproduce" >> >> Thanks for stepping forward and volunteering, Josh! >> >> Seriously, we need to get the bug list under control, it's hard to >> make out the legitimate issues among the droves of minor requests, >> weird questions, and duplicates. >> >> This isn't just blanket closing of issues, but if the issue is obscure >> and not well described, I think it is valid to add a polite message >> asking for it to be reopened when a test case is made available. >> >>> >>> On Thu, Aug 11, 2011 at 12:57 PM, Massimo Lusetti <[email protected]> >>> wrote: >>>> On Thu, Aug 11, 2011 at 9:34 PM, Howard Lewis Ship <[email protected]> >>>> wrote: >>>> >>>>> I've been trying to clean up the Tapestry issue list. If everyone >>>>> could take a peek, and help weed out duplicates and such, it would be >>>>> great. >>>>> >>>>> I'm also in a quandrary about some bugs ... I'm very tempted to mark a >>>>> bunch of bugs that date back to 5.1 or earlier as "won't fix", >>>>> especially if they are fixed in 5.3 or no longer applicable. >>>>> Thoughts? >>>> >>>> Sure that should be done especially if they're so outdated. >>>> >>>> -- >>>> Massimo >>>> http://meridio.blogspot.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] >> >> > > --------------------------------------------------------------------- > 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]
