Absolutely, I wouldn't have released it if I hadn't tested it in my own applications.
HOWEVER... The reality is that no one can test their code to 100% prefection, and the only way that all the bugs ever get wrung out is by getting banged on under stress in a variety of real-world applications. What I welcome is the the chance to get bug fixes from previous releases more rapidly into new releases, because as we know from the 1.0/1.1 epic, most commercial sites (the ones who really bang on features) won't deploy nightlies. James > -----Original Message----- > From: Martin Cooper [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 15, 2003 1:11 AM > To: Struts Developers List > Cc: [EMAIL PROTECTED] > Subject: RE: When is the next release? > > > > > On Mon, 14 Jul 2003, James Turner wrote: > > > >David Graham wrote: > > > The plan all along was that 1.2.0 would include a move to > > >commons-resources and no other major changes. However, > > >commons-resources is still in the sandbox so I suggest we > postpone > > >that move to the next release. I've committed all of my > interesting > > >changes for 1.2.0 so I'd like to hear the status on the > nested and > > >tiles bugs plus the one Martin has assigned to himself. Also, is > > >the validwhen vaildation working? > > > > > > > Well, validWhen is checked into the release, and it's the same code > > I'm using on a live customer site, so my belief is that it is. We > > won't know how well it works until more users try it out and find > > bugs, but that's the nice thing about more frequent release cycles, > > right? > > I assume you mean that 'validWhen' is checked in to CVS, and > that it's in the nightlies. It certainly isn't in a release > at this point. > > One thing I would like to be absolutely clear on. More > frequent releases absolutely does *not* mean lower quality > releases, and does *not* mean moving the burden of quality > assurance from the committers to the user base. The above > statement regarding "the nice thing" about more frequent > releases could be construed otherwise, so I felt a need to > clearly state my own position. :-} > > -- > Martin Cooper > > > > > > James > > > > > > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
