On Sun, Aug 8, 2010 at 3:46 PM, Andreas Veithen <[email protected]>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) Couple of months back I had some time to spend with Axis2 and I thought of doing a release. In fact I was expecting to do a release with the proper dependencies and what ever the possible bug fixes. Currently I am bit busy with my other stuff and if you have time please go for Axis2 1.6. Hope I will get some time another 3-4 weeks time and can do what ever necessary. BTW big +1 for the release automation process. so that any one can do a release once they got some time to spend with Axis2. Hope Saranga will be able to do the woden release soon. thanks, 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 <[email protected]> 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 ([email protected]) > > 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: [email protected] > >> Cc: [email protected] > >> Date: 08/07/2010 09:57 AM > >> Subject: Re: Next Release Axis2 1.6? > >> > >> Andreas Veithen <[email protected]> wrote on 08/07/2010 > 09:49:00 > >> AM: > >> > >> > From: Andreas Veithen <[email protected]> > >> > To: [email protected] > >> > Date: 08/07/2010 09:49 AM > >> > Subject: Re: Next Release Axis2 1.6? > >> > > >> > On Sat, Aug 7, 2010 at 16:26, Amila Suriarachchi > >> > <[email protected]> wrote: > >> > > > >> > > > >> > > On Fri, Aug 6, 2010 at 3:40 AM, Raghu Upadhyayula > >> > > <[email protected]> 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:[email protected]] > >> > >> Sent: Wednesday, May 19, 2010 3:45 PM > >> > >> To: [email protected] > >> > >> 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 unfortunately Current > >> > > Axis2 > >> > > trunk does not > >> > > compile with it. > >> > > >> > Sometimes I wonder whether the IBM folks are actually subscribed to > >> > the dev lists. I told Rich that the change he was planning would cause > >> > an additional delay for the 1.6 release -> no reaction at all. Then, > >> > his change in Axiom caused a build failure, which was reported by > >> > Hudson to the commons-dev list -> again, no reaction at all. And its > >> > not the first time that I get no answer at all to comments that I make > >> > with respect to changes done by IBM people... > >> > >> My bad, I apologize for the non-response. > >> > >> > >> > > >> > That being said, the issue caused by AXIS2-4791 is only a small part > >> > of the problem. There are still many issues to solve in the > >> > build/release process. For example, right now I'm trying to fix the > >> > source distribution so that it can actually be built... > >> > > >> > Andreas > >> > > >> > > Amila. > >> > >> > >> > >> Andreas > >> > >> > >> > >> On Wed, May 19, 2010 at 13:26, Amila Suriarachchi > >> > >> <[email protected]> wrote: > >> > >> > > >> > >> > > >> > >> > On Wed, May 19, 2010 at 3:07 PM, Hiranya Jayathilaka > >> > >> > <[email protected]> > >> > >> > wrote: > >> > >> >> > >> > >> >> Hi Folks, > >> > >> >> May I know the status of the next release? Will it be a 1.5.1 or > >> > >> >> 1.6? > >> > >> >> It > >> > >> >> would be also nice to have some dates etc to look forward to. > >> > >> > > >> > >> > would be axis2-1.6. > >> > >> > > >> > >> > Axis2 depends on several other dependencies. we need to wait > >> until axiom > >> > >> > 1.2.9 and the woden 0.9 release. > >> > >> > > >> > >> > So it may around mid june. > >> > >> > > >> > >> > thanks, > >> > >> > Amila. > >> > >> >> > >> > >> >> Thanks > >> > >> >> -- > >> > >> >> Hiranya Jayathilaka > >> > >> >> Senior Software Engineer; > >> > >> >> WSO2 Inc.; http://wso2.org > >> > >> >> E-mail: [email protected]; Mobile: +94 77 633 3491 > >> > >> >> Blog: http://techfeast-hiranya.blogspot.com > >> > >> > > >> > >> > > >> > >> > > >> > >> > -- > >> > >> > Amila Suriarachchi > >> > >> > WSO2 Inc. > >> > >> > blog: http://amilachinthaka.blogspot.com/ > >> > >> > > >> > >> > >> > >> > --------------------------------------------------------------------- > >> > >> To unsubscribe, e-mail: [email protected] > >> > >> For additional commands, e-mail: [email protected] > >> > >> > >> > >> > >> > >> > --------------------------------------------------------------------- > >> > >> To unsubscribe, e-mail: [email protected] > >> > >> For additional commands, e-mail: [email protected] > >> > >> > >> > > > >> > > > >> > > > >> > > -- > >> > > Amila Suriarachchi > >> > > WSO2 Inc. > >> > > blog: http://amilachinthaka.blogspot.com/ > >> > > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
