Because I haven't fllowed this discussion fully: +0
FWIW I agree with the sentiment expressed elsewhere that NNTP has had a number of significant minor defects in it for some time, and that this current regression defect has also not been spotted before now, ipso-fact it is not a showstopper for the majority of serious users. Therefore disabling it by default, publishing a warning and defering the bug seem to be the safest route to resolve what has all the halmarks of a conflict between two issues, and the risk of re-introducing the original problem. d. > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: 28 December 2002 16:07 > To: James-Dev Mailing List > Subject: [Vote - v2.1.0 Release] Disable NNTP by default > > > For v2.1, I propose that we disable NNTP by default, mark it as > experimental, and agree that more of us will take a look at it in v2.1.1. > > I'll start with a +1. And I believe (but could be wrong) that > this vote is > not subject to a veto, because it is a configuration default for > a release, > not a code change. > > --- Noel > > P.S. For v3, we'll have to decide what to do with NNTP and other > protocols > as we revisit repositories. > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
