Return-Path: X-Original-To: apmail-axis-java-user-archive@www.apache.org Delivered-To: apmail-axis-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D48B57D97 for ; Thu, 17 Nov 2011 19:41:11 +0000 (UTC) Received: (qmail 3253 invoked by uid 500); 17 Nov 2011 19:41:10 -0000 Delivered-To: apmail-axis-java-user-archive@axis.apache.org Received: (qmail 3205 invoked by uid 500); 17 Nov 2011 19:41:10 -0000 Mailing-List: contact java-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@axis.apache.org Delivered-To: mailing list java-user@axis.apache.org Received: (qmail 3197 invoked by uid 99); 17 Nov 2011 19:41:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2011 19:41:10 +0000 X-ASF-Spam-Status: No, hits=4.0 required=5.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sagara.gunathunga@gmail.com designates 209.85.215.173 as permitted sender) Received: from [209.85.215.173] (HELO mail-ey0-f173.google.com) (209.85.215.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2011 19:41:05 +0000 Received: by eyh6 with SMTP id 6so2837840eyh.32 for ; Thu, 17 Nov 2011 11:40:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=9YuoOsND8Wcs1MKWP3EgKn02Taw7aJYE2suUw7pXHFw=; b=g0Sl6zu3+eDMlMJDLVJp3jhyeeHFZPIXS0ypQXDSaQ/+wPBgrGjNMzll1PYr3BJ0Cn YP2GkMjB20TSmJNVsM1IuhmrPm+vulOeIbDpBVjJ4RrBGgq2/rnmVQWWgu080Cg4vZdG B/zV+7/iFdrp/vgiGZ0ZsWVy9ABUsRDoOJMAE= Received: by 10.229.61.137 with SMTP id t9mr5385508qch.181.1321558844265; Thu, 17 Nov 2011 11:40:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.46.12 with HTTP; Thu, 17 Nov 2011 11:40:23 -0800 (PST) In-Reply-To: References: From: Sagara Gunathunga Date: Thu, 17 Nov 2011 11:40:23 -0800 Message-ID: Subject: Re: Expected release date for 1.6.2 ?? To: java-user@axis.apache.org Content-Type: multipart/alternative; boundary=0016e640886e76560d04b1f3651c --0016e640886e76560d04b1f3651c Content-Type: text/plain; charset=ISO-8859-1 On Thu, Nov 17, 2011 at 11:32 AM, Andreas Veithen wrote: > Here are the things that we need to get done to do the Axis2 1.6.2 release: > > 1. Finish the 1.6.1 release cycle by releasing Sandesha2 1.6.1. The > branch is in a releasable state, so the required effort is relatively > limited. > 2. Release Axiom 1.2.13. There are 3 remaining issues in scope for > that release (2 issues that should be easy to fix and 1 that is > already done but for which some cleanup and documentation work is > still pending). There have been lots of fixes and improvements since > the previous release, so there is also some work to be done to write > the release notes and update some of the documentation. We also need > to validate that we have a working mime4j release (very likely 0.7 is > OK; otherwise we need to push the James project to do a 0.7.1 or 0.8 > release first). > During the ApacheCon I had a chat with few folks from James project about our mime4j use in Axiom project. They were very happy and they will do release or improvements if we ask. Thanks ! > 3. Release Neethi 3.0.2. The project is in a releasable state and the > required effort is limited. > 4. Release Axis2 1.6.2. Once the Axiom and Neethi releases are > available, this can be done very quickly. > > Taking into account that every release candidate needs to go through a > voting process that is open for at least 3 days I think that a > reasonable estimation for the Axis2 1.6.2 release date would be end of > December. > > Andreas > > On Thu, Nov 17, 2011 at 19:46, Alan Clark > wrote: > > > > Our application (using 1.6.1) is being severely performance limited by > the > > caching problems reported in #5119, #4878 and #4524. We understand that > > these are resolved in 1.6.2 however would very much appreciate knowing > when > > this would be available. We would also be quite happy to test this > release > > (or pre-release) and provide feedback if that would be useful. > > > > Thanks > > > > Alan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org > For additional commands, e-mail: java-user-help@axis.apache.org > > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara --0016e640886e76560d04b1f3651c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Nov 17, 2011 at 11:32 AM, Andrea= s Veithen <andreas.veithen@gmail.com> wrote:
Here are the things that we need to get done to do the Axis2 1.6.2 release:=

1. Finish the 1.6.1 release cycle by releasing Sandesha2 1.6.1. The
branch is in a releasable state, so the required effort is relatively
limited.
2. Release Axiom 1.2.13. There are 3 remaining issues in scope for
that release (2 issues that should be easy to fix and 1 that is
already done but for which some cleanup and documentation work is
still pending). There have been lots of fixes and improvements since
the previous release, so there is also some work to be done to write
the release notes and update some of the documentation. We also need
to validate that we have a working mime4j release (very likely 0.7 is
OK; otherwise we need to push the James project to do a 0.7.1 or 0.8
release first).

During the ApacheCon I had a chat = with few folks from James project about our mime4j use in Axiom project. Th= ey were very happy and they will do=A0 release or improvements if we ask. <= br>
Thanks !
=A0
3. Release Neethi 3.0.2. The project is in a releasable state and the
required effort is limited.
4. Release Axis2 1.6.2. Once the Axiom and Neethi releases are
available, this can be done very quickly.

Taking into account that every release candidate needs to go through a
voting process that is open for at least 3 days I think that a
reasonable estimation for the Axis2 1.6.2 release date would be end of
December.

Andreas

On Thu, Nov 17, 2011 at 19:46, Alan Clark <alan.d.clark@telchemy.com> wrote:
>
> Our application (using 1.6.1) is being severely performance limited by= the
> caching problems reported in #5119, #4878 and #4524. =A0We understand = that
> these are resolved in 1.6.2 however would very much appreciate knowing= when
> this would be available. =A0We would also be quite happy to test this = release
> (or pre-release) and provide feedback =A0if that would be useful.
>
> Thanks
>
> Alan

---------------------------------------------------------------= ------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org




--
Sagara Gunathunga
Blog =A0 =A0 =A0- http://ssagara.blogspot.com
Web =A0 =A0 =A0- http://people.apache.org/~sag= ara/
LinkedIn - http://www.linkedin.com/in/ssagara
--0016e640886e76560d04b1f3651c--