On Sun, Aug 8, 2010 at 16:14, Deepal Jayasinghe wrote:
> I would like to add few more items, we need to make sure Axis2 works
> with current version of rampart and sandesha, making sure Web
> distribution and other distribution works fine. I have seen people
> complaining about Idea and Eclipse plugin so we need to test them too.
As I said, no light at the end of the tunnel :-(
> I think we have a wiki page mentioning the release process.
>
> http://wiki.apache.org/ws/FrontPage/Axis2/release_process
> http://wiki.apache.org/ws/FrontPage/Axis2/releases/steps
I guess the emphasis should be on "mentioning"... Just to give you an
example of the kind of info that is missing: there are (or were,
before my changes) several places other than the elements in
the POM files where the version number is hardcoded. To do a correct
release, you need to know that and make sure that all these files are
updated. Note that my goal is to eliminate these things and make sure
that the entire build process calculates version numbers based on the
POM files. For example, for the Eclipse plugins I changed the build
process to use maven-bundle-plugin which takes care of generating an
OSGi compliant version number from the Maven version. This also solves
the issue with the dependencies in the plugin.xml file, which
sometimes get out of sync with the Maven dependencies.
> Deepal
>
> On Sun, Aug 8, 2010 at 6:16 AM, Andreas Veithen
> wrote:
>> Here is the complete story:
>>
>> Normally, the release process should be as simple as this:
>>
>> 1. Update relevant documentation (release note, entry in the download
>> page, etc.) for the release.
>> 2. Use maven-release-plugin to perform the release and upload the
>> artifacts to the (Nexus) staging repository.
>> 3. Vote.
>> 4. Promote the Maven artifacts for the release.
>> 5. Upload the distributions.
>> 6. Upload the site.
>> 7. Send an announcement.
>>
>> However, with Axis2, it is far from being that simple. I guess that
>> former Release Managers can confirm that previous releases have always
>> caused much headaches. Unfortunately nobody ever took the time to
>> document the process. Currently, my primary goal is to fix the
>> build/release process to get 1.5.2 out. Obviously it would not make
>> sense to fix this only on the 1.5 branch. Therefore I'm doing the
>> changes on the trunk (with the 1.6 release in mind, which BTW is still
>> officially managed by Amila) and then merge them to the 1.5 branch.
>>
>> To answer your question: the plan is to release 1.6 with Axiom 1.2.9.
>> Ideally we should have a 1.6 branch (depending on Axiom 1.2.9) where
>> we prepare the release, and development should go on on the trunk
>> (depending on Axiom 1.2.10-SNAPSHOT). However, that would mean that
>> the changes to the build/release process would have to be merged
>> twice. That is something I would like to avoid.
>>
>> I don't think there is a need for a contribution freeze, but changes
>> that depend on new features in Axiom 1.2.10 should be postponed until
>> we have a 1.6 branch, i.e. until the build/release process has been
>> stabilized.
>>
>> Andreas
>>
>> On Sat, Aug 7, 2010 at 17:07, R J Scheuerle Jr wrote:
>>> Andreas,
>>>
>>> Will Axis2 1.6 be based on Axiom 1.10 ? That has been my assumption.
>>>
>>> I am discussing a contribution freeze with the other IBM committers.
>>>
>>> Thanks,
>>>
>>> Rich Scheuerle
>>> Senior Programmer, AIM SWG
>>> IBM Web Services (JAX-RPC, JAX-WS, SAAJ)
>>> Development, Customer Solutions, and Open Source
>>> Apache Axis2 (sc...@apache.org)
>>> 512-286-8420 (IBM TL 363-8420)
>>>
>>> R J Scheuerle Jr/Austin/i...@ibmus wrote on 08/07/2010 09:57:01 AM:
>>>
From: R J Scheuerle Jr/Austin/i...@ibmus
>>>
To: java-dev@axis.apache.org
Cc: java-dev@axis.apache.org
Date: 08/07/2010 09:57 AM
Subject: Re: Next Release Axis2 1.6?
Andreas Veithen wrote on 08/07/2010 09:49:00
AM:
> From: Andreas Veithen
> To: java-dev@axis.apache.org
> Date: 08/07/2010 09:49 AM
> Subject: Re: Next Release Axis2 1.6?
>
> On Sat, Aug 7, 2010 at 16:26, Amila Suriarachchi
> wrote:
> >
> >
> > On Fri, Aug 6, 2010 at 3:40 AM, Raghu Upadhyayula
> > wrote:
> >>
> >> Hi,
> >>
> >> What is the status of the Axis2 1.6 release?? What's a
> >> tentative
> >> date for the release??
> >>
> >> Thanks
> >> Raghu
> >>
> >>
> >> -Original Message-
> >> From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
> >> Sent: Wednesday, May 19, 2010 3:45 PM
> >> To: java-dev@axis.apache.org
> >> Subject: Re: Next Release?
> >>
> >> Work on Axiom 1.2.9 is progressing. I'm now in the process of
> >> reviewing some of the stuff that has been introduced since 1.2.8, in
> >> order to make sure that these APIs are consistent.
> >
> > Now Andreas has done Axiom 1.2.9 release. But unfortun
