On 1/18/01 12:30 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> 2. It seems he made a distinction between +1 ( I support the plan or
> release ) and "commited" +1 ( I support the plan _and_ I commit to help).
>
> 3. My vote will be a "commited" +1.
My reading of the situation is that if y
> At 12:30 18/1/01 -0800, [EMAIL PROTECTED] wrote:
> >2. It seems he made a distinction between +1 ( I support the plan or
> >release ) and "commited" +1 ( I support the plan _and_ I commit to help).
>
> I understood the first case to be a +0 - ie nice idea but I ain't gonna put
> any effort in
At 12:30 18/1/01 -0800, [EMAIL PROTECTED] wrote:
>2. It seems he made a distinction between +1 ( I support the plan or
>release ) and "commited" +1 ( I support the plan _and_ I commit to help).
I understood the first case to be a +0 - ie nice idea but I ain't gonna put
any effort into maintainin
> i havent been following this for some time now, but if
> i remember correctly, 3.x supported jdk1.1.
Support for JDK1.1 is included in the release proposal, as well as
testing.
--
Costin
-
To unsubscribe, e-mail: [EMAIL PRO
> My personal feeling about this as a Jakarta (but not Tomcat) Committer
> is that the requirement for three binding (+1) votes before a public
> release is there to address the support issues. A (+1) vote on a public
> release should mean that you are signing-on for future development and
> supp
i havent been following this for some time now, but if
i remember correctly, 3.x supported jdk1.1 and 4.x
didnt. this is a major concern to me. the company i
work for would like to deploy tomcat on the as400. im
not an as400 guru, so i dont know if they have a jdk
yet that supports 1.2, all i know
My personal feeling about this as a Jakarta (but not Tomcat) Committer
is that the requirement for three binding (+1) votes before a public
release is there to address the support issues. A (+1) vote on a public
release should mean that you are signing-on for future development and
support. In thi
I'm a user and I rightly don't get a vote
(and might do better to keep quiet!) but I think releasing a version 3.3 would be bad for the project unless the
concerns about support can be fully resolved. This is so even though it seems to be agreed that the basic code itself
is technically supe
