on 12/27/2000 11:58 AM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
> Likely waiting for the release manager at the time (me) to do his job.
> Craig indicated at the time that he was able to get relief from his
> employer to spend work time on putting out the 3.2 release - something we
> all very much appreciate.
Point being that this is a volunteer organization and anyone, at any point
(voted on of course) can stand up and do a release. In other words, Costin
found time to work on 3.3, but didn't find time to either do a release or
help Craig do a release.
>> This will get finalized at the PMC meeting I'm
>> sure, but as far as I see it, we had an agreement
>> within the group that the future would be Catalina
>> and the compromise hasn't been made yet and I'm
>> calling attention to the fact that people are
>> ignoring what we decided upon earlier.
>
> Can somebody point me to the mail archives where this decision was made?
>
> The existing jakarta-tomcat module is proposed to continue as it
> currently exists (except for being renamed), for use in supporting the
> Tomcat 3.x code for as long as this is appropriate.
Nope. I think that is why the PMC meeting is being called. To clear this up
once and for all. There was some good discussion under the subject: "Tomcat,
Catalina, and Java2", but I didn't save it all and I didn't see a final
decision there. Maybe I'm even incorrect with my statement however, the path
that I "felt" we were going down was having Catalina be Tomcat 4.x and I
haven't seen anyone really object to that yet (especially given that that is
the CVS module name for Catalina). The issue has been to this point what
will be Tomcat 3.3 (if anything).
thanks,
-jon