Bases on the release early, release often criteria, maybe it makes sense to get the rest of Corey's unit tests patches in, and spend a bit of time verifing all the javadocs etc. Then do a 1.0 of whats there. That way we don't have to be quite as contrained by the existing API, as projects that depend on email will have a nice released version that they can use.
This also might be the time to migrate out of the sandbox? > -----Original Message----- > From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 3:44 PM > To: 'Jakarta Commons Developers List'; 'Corey Scott' > Subject: RE: [email] Anyone interested? > > > my > +1 too > > > -----Original Message----- > > From: Corey Scott [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 26, 2004 3:29 PM > > To: Jakarta Commons Developers List > > Subject: Re: [email] Anyone interested? > > > > > > I think this is a great idea!! > > -Corey > > > > > > Hi, > > > These ideas are all very interesting. I would just caution against > > > falling into the same pits experienced by [configuration] > > and [math]: > > > that is, endlessly debating/adding features, refactoring, > > etc, before > > > ever making a release. It might be good to get a 1.0 release out > > > there and then discuss/act upon these new ideas for 1.1 or 2.0. > > > Release early, release often is always my vote ;) > > > > > > Yoav Shapira http://www.yoavshapira.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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
