Sorry I missed all of the discussions on the PMC list. I'll be watching more closely today.
> (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 I think we want to stay with Jakarta. For the moment I see no benefit in moving. Whatever we end up doing we should keep the name and product HttpClient, but it may just be one part of what we do. Another part will be the various reusable HTTP components http-common, http-cookie, etc. The big question is what "finished" products other than HttpClient can we create using the components. Technically we can do a lot, politically it may be a trickier question. Let's continue to look at this. > (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 We can stay or move, I have no great love for either. > (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? I would prefer to not have another RC release, but it we think it's necessary I can certainly manager. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
