Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 56799 invoked from network); 8 Jan 2004 10:42:19 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Jan 2004 10:42:19 -0000 Received: (qmail 47369 invoked by uid 500); 8 Jan 2004 10:41:52 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 47351 invoked by uid 500); 8 Jan 2004 10:41:52 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 47338 invoked from network); 8 Jan 2004 10:41:51 -0000 Received: from unknown (HELO KCCXOEX11.corp.kpmgconsulting.com) (57.80.136.23) by daedalus.apache.org with SMTP; 8 Jan 2004 10:41:51 -0000 Received: from kccxoex06.corp.kpmgconsulting.com ([10.98.3.31]) by KCCXOEX11.corp.kpmgconsulting.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 8 Jan 2004 10:41:25 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Next Release? Date: Thu, 8 Jan 2004 10:42:03 -0000 Message-ID: <825BF35A92B3F0479CC164ECBBE9376E5F02EB@kccxoex06.corp.kpmgconsulting.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Next Release? Thread-Index: AcPV0y/4FfSq6UhpSb6ZWjyg7X+ZvQAABTmQ From: "Kalnichevski, Oleg" To: "Commons HttpClient Project" X-OriginalArrivalTime: 08 Jan 2004 10:41:25.0593 (UTC) FILETIME=[F709B490:01C3D5D3] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Makes sense. Anyways, some sort of coherent statement with regards to = the post-2.0 development directions is pretty much a must for the 2.0 = Final. I think I could handle this task while you, guys, concentrate on = reviewing the pending patches, even though I am a terrible writer. Oleg -----Original Message----- From: Ortwin Gl=FCck [mailto:ortwin.glueck@nose.ch] Sent: Thursday, January 08, 2004 11:36 To: Commons HttpClient Project Subject: Re: Next Release? Looking at Bugzilla there are a few bugs with target milestone 2.1 Final = and 3.0 Final. We can at least summarize these up or just provide links=20 to Bugzilla. This is at least some sort of minimal planning. Also your quote to Srinivas could go on that page. I means if we all=20 have ideas about a schedule in our heads. It's just a matter of=20 communicating them. But nobody will ever point their finger at us if we=20 do not stick to those plans and change them for good reason. Odi Kalnichevski, Oleg wrote: > Odi, > That would surely be a much welcome addition. However, up to now we = have not been terribly good at planning things in advance and then = sticking to what has been agreed upon. With the current limited resource = pool I can hardly see anything more 'we wanna make HttpClient better' = kind of roadmap we would manage to live up to >=20 > Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org