On Fri, 2007-06-29 at 21:26 +0100, Stephen Colebourne wrote:
> Roland Weber wrote:
> > 1. Keep the httpclient site with the rest of commons
> > and move it to the new TLP domain. We'll have to update
> > the httpclient build with the new location and redeploy.
> > (Anything I've forgotten?)
> > 
> > 2. Move the httpclient site to httpcomponents. Since
> > httpcomponents is unlikely to remain in Jakarta
> > indefinitely, that means the site would move again
> > later this year. Two moves within a few months is a
> > bit too disruptive to users for my liking.
> > 
> > 3. Keep the httpclient site at it's current location
> > in Jakarta when the rest of the commons site moves.
> > Move it only once to httpcomponents when those leave
> > Jakarta.
> 
> The question is really whether the Commons TLP owns the HttpClient 
> codebase.

Stephen et al

Based on the project's charter approved by the Jakarta PMC on Oct 31st,
2005 the HttpComponents project is meant to have the ownership of the
Commons HttpClient codebase

http://svn.apache.org/repos/asf/jakarta/httpcomponents/project/project-charter.txt

It all did not matter much while we were still one (more or less) happy
family.

My preference is to not not move stuff around (option 1). I am planning
to cut HttpClient 3.1 final release shortly after HttpClient 4.0 alpha1.
3.1 is very likely to be the last release of the HttpClient 3.x codebase
unless some serious security or legal problems are found. There is no
point in investing a lot of efforts into a codeline, which is going to
become dormant very soon. 

Oleg

>  I don't believe its terribly sensible for it to do so. All 
> active committers and knowledge are focussed in the HttpComonents group.
> 
> Thus I would suggest #3 as the best option, followed by #2.
> 
> Stephen
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to