You might at least want to start those discussions about the checkstyle settings, so that we can develop a strategy about how they would be fixed the next time there is a window of opportunity.
When I did a a time study in February, curing the the current errors with the current settings would take at least 40 hard hours. We need to find a way to do the work faster, or get more people to work on it. (We probably should have made this a Google Summer of Code project.) There is also the issue of how we want to handle the exception issues. We will be addressing exception handling in SAF 2, so it's a pertinent question. We might also consider fixing some of the errors at a time, for example maybe just the exception handlers. That could have less of an impact that trying to cure all six thousand at once. -Ted. On 6/15/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
Ok, my head is spinning :) I like simple, so, I'll say the same thing I remember saying months ago... just ping me when the time is right to deal with Checkstyle complaints, and so long as I still have some free time then, I'll do it. You have someone willing to do the work, I'll let you worry about the timing issues :) Frank On Thu, June 15, 2006 12:46 pm, Ted Husted wrote: > The problem is patches. People will tend to write patches against > whatever version they are using. If we make a lot of changes right > after a popular release, then a lot of the patches people submit back > won't work. The ideal time for broad refactorings is at the beginning > of a minor series (pre #.0.0), rather than in the middle of several > point releases(. > > In the grand scope, it would be better if Niall could roll 1.3.5 now > rather than wait. If this milestone works out, then we might have to > target 1.4 for the next round of pro-forma refactorings. > > -Ted. > > On 6/15/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: >> Ok, cool Niall... I guess we maybe need to decide what the "wait point" >> really is here... do we want to wait for GA before I generate these >> patches, or just the next release? At first I thought Ted was saying >> let's wait for GA, but then it sounded like maybe just wait for 1.3.5 >> (which may or may not be GA of course!). It's cool with me either way, >> just want to make sure we're all on the same page... no sense in me >> doing >> work that will either take a long time to get applied (I'm assuming >> someone *will* apply them), or possibly have to be re-done anyway >> because >> a release or two maybe makes them invalid. >> >> Frank >> >> >> -- >> Frank W. Zammetti >> Founder and Chief Software Architect >> Omnytex Technologies >> http://www.omnytex.com >> AIM: fzammetti >> Yahoo: fzammetti >> MSN: [EMAIL PROTECTED] >> Java Web Parts - >> http://javawebparts.sourceforge.net >> Supplying the wheel, so you don't have to reinvent it! >> >> On Thu, June 15, 2006 11:21 am, Niall Pemberton wrote: >> > On 6/15/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: >> >> On Thu, June 15, 2006 6:35 am, Ted Husted wrote: >> >> >> >> > In the meantime, that would give Frank time to work on those >> patches. >> >> >> >> So you don't want to wait for GA now? That's fine with me... I'm not >> >> sure >> >> I can take care of all the complaints by July, but I should be able >> to >> >> get >> >> rid of enough of them to make it worth doing (the two things I >> mentioned >> >> the other day would probably cut the numbers in half alone, and >> they're >> >> low-hanging fruit I think). >> > >> > I'm going to try and find time for 1.3.5 next week - it may not >> > happen, but if I can then IMO better to leave till after. >> > >> > Niall >> > >> >> > -Ted. >> >> >> >> Frank >> > >> > --------------------------------------------------------------------- >> > 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] >> >> > > > -- > HTH, Ted. > * http://www.husted.com/struts/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
