Folks,

There are three issues that I think we need to discuss:

(1) I inquired with the Jakarta PMC regarding the possibility of the project 
name change (Jakarta HttpClient -> Jakarta Http). The reaction was overwhelming 
negative, primarily due to high likelihood of branding conflict with Apache 
HTTPD, which is a very valid point. We have several options here: 

(1.1) leave Jakarta and join another TLP (either Apache Tomcat or Apache HTTPD) 
where _might_ be permitted to call the project jHTTP or some such sort
(1.2) stay with Jakarta and try to come up with a radically different project 
name
(1.3) essentially do nothing and keep the same name. In this case we are likely 
to not be permitted to release any lightweight HTTP server or proxy under 
Jakarta name

(2) Migration to JIRA. This finally can happen and happen very soon. The 
question is if we still want it. If yes, might have to decide on the project 
name before the migration takes place

(3) 3.0 release. 3.0rc3 have not had any major bugs reported for quite some 
time. Do we want to release another RC4 before the final release or not?

Please let me know what you think. Everyone is very welcome to throw in their 
ideas

Cheers,

Oleg
PS: Henri, I took liberty of putting you on the CC to keep you in the loop. I 
hope it is okay with you

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

Reply via email to