axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Sosnoski <>
Subject Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
Date Tue, 15 May 2007 20:36:22 GMT
I think skipping 1.2.1 is a bad idea. So far each major Axis2 release 
has gone out with critical bugs found shortly after release. A 1.2.1 
release will at least fix these critical bugs for 1.2 (hopefully without 
creating a bunch of new ones). Just moving to 1.3 from trunk, on the 
other hand, is likely to create at least as many new critical bugs as it 

We really need better quality control for Axis2 to achieve the level of 
use it deserves. When 1.3 does come out I'd hope it would be subject to 
more rigorous testing than what has gone before. I'd suggest that for 
this one we do a more realistic release progression, starting with a 
branch and a beta release from that branch, then moving on to a release 
candidate once we really think the code is solid - and holding at that 
release candidate for at least a couple of weeks of final testing before 
the official release.

The Rampart process should follow the same path and same schedule. I'm 
starting to wonder if it even made sense to split Rampart out of the 
Axis2 codebase, since I don't think there's much point in doing an Axis2 
release without a corresponding Rampart release. The current situation 
of having an Axis2 1.2 release with no corresponding Rampart release 
means that most enterprise users are stuck back at Axis2 1.1.1 (the 
working version of 1.1, and the last release for which WS-Security is 

  - Dennis

Davanum Srinivas wrote:
> Glen,
> Makes sense to me. Let's skip 1.2.1 and jump straight to the next
> release from trunk. Since we need new releases of Axiom, XmlSchema,
> the so called "critical" bugs don't seem so critical anymore :) We
> should have a 1.3 real-soon-now instead of waiting too long.
> Folks,
> thanks,
> dims
> On 5/15/07, Glen Daniels <> wrote:
>> At this point I feel I have to ask why are we doing 1.2.1 from the
>> branch and *not* just moving ahead on the trunk?  It seems like about
>> the same amount of effort now... if 1.2.1 were just fixing a few
>> critical problems with 1.2 and then releasing ASAP, that would be fine,
>> but if it involves changing Axiom and Schema dependencies as well, why
>> not just take the time to get the fixes into trunk and do the release
>> from there (with another branch for 1.2.5 or whatever we end up 
>> calling it).
>> I'm OK with it either way but the more work that happens over on the
>> branch, the more likely it is that something will get dropped when we
>> move back to trunk....
>> Thoughts?
>> --Glen
>> Deepal Jayasinghe wrote:
>> > Hi Dennis,
>> >
>> > Now the release process is bit complex and we need to release 
>> dependent
>> > projects before Axis2 release (specially Axiom and XML Schema ) so 
>> I can
>> > not exactly tell the release date of Axis2 1.2.1. Any way let's try to
>> > do is as soon as we can.
>> >
>> > Thanks
>> > Deepal
>> >
>> > Dennis Sosnoski wrote:
>> >> I'd like to get this one fixed for 1.2.1, too:
>> >>
>> >>
>> >> Can anyone give a target date for the 1.2.1 release? I'm planning to
>> >> have this fixed within two days, but want to make sure I don't miss
>> >> the release window.
>> >>
>> >>  - Dennis
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> > For additional commands, e-mail:
>> >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message