Re: James and NNTP Server. We should address this before 2.1 release.

[Serge Knystautas]

Well, I have to say this is a very tough situation.

I completely see Harmeet's point that people shouldn't break code... I believe that like doctors, open source developers should follow the Hipocratic oath (specifically the part about doing no harm).

But 2.1 has been sitting for some time, and while it might take Harmeet only a week or so, we're getting into a very slippery slope. I feel guilty for the file repository fix in that it has opened the door for reevaluating what's in 2.1.

I would prefer to release 2.1 as is (a.s.a.p.) with a big warning that it does not support NNTP just yet, branch the code, have Harmeet (or whoever) fix NNTP, we continue to make point releases on the 2.1 branch, and let others start working on other issues. But, while we release 2.1 (meaning put out as a final public release on Jakarta's site), we hold off making the announcement in external sources (the so-called PR campaign), until NNTP is fixed.

--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>