Unfortunately, we keep changing the artifact names and Plugin architecture/schema in every major release, so users who have developed real JavaEE apps on 2.0 (more than just simple servlet/jsp web apps) will more than likely have some work and testing before they can move to 2.1.

If we want to build a vibrant user community, we need to support the prior major release (2.0) until our next major release (2.2) comes out.


-Donald

Jacek Laskowski wrote:
On Thu, Feb 21, 2008 at 10:36 AM, Erik B. Craig <[EMAIL PROTECTED]> wrote:

 I have had this thought myself. Often times it seems we are far more
 focused on the next major release (I.E. current trunk) as opposed to
 introducing some more necessary fixes into other smaller releases. I
 think we should definitely continue to support / release on the 2.0
 branch as much as possible, and would be happy to assist in
 integration of patches and changes that have been made since then.

I always thought that our support for past releases has been the
latest release. It will lower the burden greatly for us and for our
users too. If we put more attention to documentation *and* release
often with small changes they would benefit more.

Jacek

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to