I agree this makes sense. I am not sure, though, whether we can
reasonably expect things to happen in one 'Big Bang': mailing lists, new
CVS repository, web site, JIRA migration and so on. Most likely not.
Another question is if we want to switch to Subversion when we go to 4.0. It sounds like Jakarta is moving in that direction. Also, if we're going to switch repos and change our package name it would seem like a good time.
I agree that it may be difficult to do all these things at once, but I think if we start doing things now it shouldn't be too painful. The next item to move is probably the mailing list. This has been on my TODO list for a while now. I'll email infrastructure tonight and get the ball rolling.
Besides, unless we start getting MASSIVELY more feedback on 3.0, I am
not sure what else we can do but start hacking on 4.0 branch while 3.0
still goes through its natural development cycle: alpha -> beta -> rc ->
release. I sense the work on 4.0 may well commence as early as next
month. Basically that will buy us some time, but not much. I certainly
want to start the discussion on the 4.0 architecture (at least in broad
strokes) very, very soon.
Next month seems pretty soon, but I guess you never know. My guess was that it wouldn't happen until January. We definitely want a pretty solid plan before we get started though.
This, again, makes the issue of issue tracking system highly important,
as we better have a sane road map and reasonably well articulated
strategy as soon as people start asking what the heck Jakarta HttpClient
4.0 is all about and how on earth we ended up with 3 API incompatible
branches.
Yes, I'm not looking forward to 3 supported APIs at the same time. Hopefully 2.0 will be mostly frozen by the time 4.0 gets started.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
