Dennis, "ADB unwrapping" and JAXB codegen are not super-critical IMHO. If i see JIRA's from users clamoring for these, then i am likely to change my opinion. These are my 2 cents. I definitely agree about backward compat and documentation changes.
thanks, dims On 5/15/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
ADB unwrapping was broken, which seems pretty critical to me. I know Amila fixed that, though I don't know if he created a Jira on the issue. The JAXB code generation was also broken, at least for cases with multiple schemas in the WSDL. I don't know the status of that one. Those are the problems I've personally encountered in some limited testing with the 1.2 release. Aren't there also a number of problems in the schema handling for WSDL2Java? But at this point we can't even test Rampart with 1.2, AFAIK. If Rampart can do a 1.2 release without changes to Axis2 1.2 then perhaps it's reasonable to stay with the existing 1.2. In the future I don't think it makes sense to do an Axis2 release at all without at least working test builds of Rampart for that release. To say that it's a separate mar is just begging the issue - Rampart provides core functionality for enterprise users of Axis2, and the code is so intimately tied to the Axis2 and AXIOM code that you need a specific build of Rampart to match an Axis2 release. That's why I now think it was a mistake to split it out of the Axis2 codebase - by doing so we've created the need for a lot more coordination without any gains in flexibility that I can see. My feeling is that for Axis2 to be usable in enterprise environments the releases need to be maintained with critical fixes. I've been doing this for the axis2-jibx module myself, since that's easily handled in isolation. I also don't think we should break backward compatibility unless it's absolutely necessary, and if compatibility is broken we should document it as part of the release notes. - Dennis Davanum Srinivas wrote: > Dennis, > > Do you have a list of critical bugs from 1.2? that needs to be fixed? > All bugs i have seen so far have some sort of work around. > > Rampart is not part of Axis2 codebase. There is nothing stopping > rampart folks from shipping a mar for Axis2 1.2. > > thanks, > dims > > On 5/15/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote: >> 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 >> fixes. >> >> 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 >> available). >> >> - 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, >> > WDYT? >> > >> > thanks, >> > dims >> > >> > On 5/15/07, Glen Daniels <[EMAIL PROTECTED]> 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: >> >> >> https://issues.apache.org/jira/browse/AXIS2-2669 >> >> >> >> >> >> 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: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> 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] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas :: http://davanum.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
