On Mon, 2004-06-07 at 19:29, Dennis Cook wrote: > I was wondering when httpclient will be moved out of commons to the > sub-project level?
Dennis, This issue has never been formally voted on, so take it as my personal option only. I think it does not make sense to release HttpClient 3.0 out of Jakarta Proper. Rather it should be released out of Commons, thus avoiding lots of thorny issues such as binary compatibility with new package structure. Jakarta HttpClient should not contain any ugly legacy code (no bloody HttpMethod interface and stuff). This is a unique chance for us to radically redesign HttpClient's API without creating too much of a confusion. This, of course, may take months if not years It does not mean, though, we should not be leveraging our new status right now. We should get some web presence on the Jakarta level (rather sooner than later), get new mailing lists set up, and position HttpClient as a first class Jakarta citizen. The whole migration process is currently stalled because Bugzilla migration turned out to be a major problem. http://issues.apache.org/jira/browse/INFRA-74?page=history If there's no progress made on the Bugzilla migration front in two to three weeks time, we'll have to consider radical steps, ranging from marking the existing tickets in Bugzilla as read-only and manually migrating open issues to Jira to running two bug tracing systems in parallel (Bugzilla for Commons HttpClient and Jira for Jakarta HttpClient) Cheers, Oleg > > Dennis Cook > BeVocal, Inc > tel: 650-641-1424 > fax: 650-210-9275 > > > --------------------------------------------------------------------- > 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]
