Andrew, If you feel there's something glaringly wrong that should be improved, patches are always greatly welcome.
For my money, the only thing that should hold up a release is a volunteer saying they will fix something but won't have it ready until date X. Beyond that, changelogs go out with all the contributors and committers names on them... believe me, they're not looking to put out a bad product and just are trying to find a balance. Serge Knystautas Loki Technologies http://www.lokitech.com/ ----- Original Message ----- From: "Andrew C. Oliver" <[EMAIL PROTECTED]> Newsgroups: gmane.comp.jakarta.james.devel To: <[EMAIL PROTECTED]> Sent: Sunday, August 18, 2002 11:21 PM Subject: Re: about javadocs (was: Re: FW: What do we need to release 2.1?) > To be honest Tetsuya, it makes me scared to use it. Javadoc to me is so > basic and takes so little time, to actually argue against it... To me > this is the same as an argument to write variables a1, a2, a3... Its > code quality. This is an active argument for poor code quality and I > can't believe this is controversial! > > Tetsuya Kitahata wrote: > > On Sun, 18 Aug 2002 20:40:35 -0400 > > "Noel J. Bergman" <[EMAIL PROTECTED]> wrote: > > > > > >>Everyone is agreeing that the documentation is necessary. But javadocs for > >>developers is not a reason to hold end users hostage. > > > > > > I love this sentence, "But javadocs for developers is not a reason to > > hold end users hostage". > > > > I think documentation is VERY important, however, in my position > > just exernal documents (for users) not necessarily internal ones > > (javadocs). > > > > Sorry for the interruption. > > > > -- Tetsuya Kitahata <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
