+1 from me!

I'm using in production the various 2.2.0.ax since the very beginning, and
they have been always super, and much stronger then 2.1.3.
Currently I have in production 2.2.0a15, so I haven't tested 2.2.0a18 at
all, but I "swear" at least up to a15 :-)

I'm only sorry for not having helped too much in the last few months, but
I really want to in the near future!

Vincenzo

> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: venerdi 16 aprile 2004 17.52
> To: James Developers List
> Subject: RE: Vote to officially release a18 build
>
>
> I am eager to get v2.2.0 out the door and done, but we know that there
is a
> short list of outstanding defects.  Plus there are defects already fixed
for
> the next drop, which I was planning to do today.
>
> Fixes already made since a18:
>
>         InetAddress caches without regarding to DNS TTL.  Switch to
using
>         dnsjava Address.get[All]ByName.  Eventually we should look at
using
>         JNDI for DNS services, at least in the Mailet API.
>
>         Fix for JAMES-9
>         Fix for JAMES-96
>         Fix for JAMES-144
>         Fix for JAMES-240
>         Fix for JAMES-247
>         Fix for JAMES-253
>         Fix for JAMES-255
>
> I just created a version 2.2.0 to assign issues to for the RoadMap.
After a
> quick pass through all of the unresolved issues, I marked 5 issues for
> 2.2.0.  Others seemed much more involved, and not critical for the
majority
> of users.  I want to fix JAMES-239 and JAMES-238, which I hope to do
today
> as soon as the jackhammer operators finish.  I will also look at the two
for
> which we have contributed patches.  I'll try to have everything except
for
> JAMES-99 done by late tonight.  Soren and Steve are going to finish
JAMES-99
> this weekend, I believe.  That's the whole list, and I think it makes
sense
> to resolve them, and then ship 2.2.0.
>
> Of the ones not scheduled to fix, several are related, not all are bugs,
and
> I did not spot any that need to be fixed in 2.2.0, although I plan to
focus
> on the memory issue as soon as 2.2.0 is final.
>
> I'd like for Steve Short to take a look at JAMES-155, since he
apparently
> uses Oracle (http://nagoya.apache.org/jira/browse/JAMES-155).  It isn't
a
> bug, so I plan to close it, but it would be nice to give the guy an
answer.
>
>       --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to