Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of ben.speakmon@gmail.com
 designates 209.85.132.245 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=YRSrO2FWgqBasIk5W5laSZpIm9dk8RyYyprJIuDvbBW2dygppMjZCEII3Cual4/CIdoUgdcv9J6Im4Qh8KMy0rRuvanKqwpmIEKBbElFu3VBkFJve29W/T6mMztib6DQdcl940X1KamKKcIbO7bn2/1gL4r36FdETqGQeLW3GMg=
Message-ID: <953ab5ae0702011034n2742329dja46c092c4f67f5b6@mail.gmail.com>
Date: Thu, 1 Feb 2007 10:34:02 -0800
From: "Ben Speakmon" <ben.speakmon@gmail.com>
To: commons-dev@jakarta.apache.org
Subject: Re: [email] Status and JIRA breakdown
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 1/31/07, Henri Yandell <flamefew@gmail.com> wrote:

> > > 1 bug: HTML Emails with images don't display in Outlook 2000
> > > (https://issues.apache.org/jira/browse/EMAIL-50)

> I've left a comment on that issue previously about the initial patch,
> and I'm not sure if the second patch provides all that is needed to
> fix the issue (anyone tested it?)

Unfortunately (or is that fortunately?), I don't have access to Outlook 2000.

> > > 2 features: adding SSL support and generating Email objects from
> > > InputStreams or Strings (both of which seem useful)

> Yep, these seem useful - I'll look at them now.

> > +1 to 1.4/1.1 and +1 to small improvements rather than any big rethinks.
> >
> > In your opinion - should all the issues be fixed for 1.1? Or should
> > some be wontfix'd or aren't worth the effort?

I think that all of the currently open issues are either bugs in
existing functionality or worthwhile and simple enhancements that
don't break source compatibility. Both categories sound like the kind
of thing that should go into a point release, so at the moment I say
they should all go into 1.1.

> Let's get a 1.1 plan happening.

I'd be happy to help with this as well.

Also, I did turn up one more important bit of info: jaf 1.1 and
javamail 1.4 require at least Java 1.4, so committing to those
dependencies means that a commons-email 1.1 wouldn't be usable on Java
1.3. Just wanted everyone to be aware :)

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org