Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
My $0.02: * If there is indeed a list of quick, critical fixes, then those can and should be fixed and we should do a 1.2.1 release from the 1.2 branch. I'm +1 for this as long as we're careful about the next point. * Anything that gets fixed on the 1.2 branch should also be fixed on the trunk, if it's not already. Ideally the fix should actually happen in the trunk and be merged over to the branch where possible. * The trunk should keep moving forward, working towards 1.3 in the relatively near future regardless. We should start collecting line-items for what we'd like to see by the time 1.3 goes out. Thanks, --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
David, Dennis, Anyone else, If someone posts an exact plan with specific JIRA's to be fixed. So far there's just thoughts and pointers to here and there. Please start a wiki page and collate the *EXACT* list of JIRA's. and then start a VOTE thread when you are ready. Till then, am personally going to go on working on the trunk. Please note that you will have to have JIRA's for axiom and xmlschema as well (if any!) thanks, dims On 5/16/07, David Illsley <[EMAIL PROTECTED]> wrote: I agree with Dennis that skipping 1.2.1 just because we can do a 1.3 is a bad idea. If there are a months worth of fixes for small problems on the branch lets release it and give our users something of a higher quality to use for the next few months. David On 16/05/07, Afkham Azeez <[EMAIL PROTECTED]> wrote: > +1 for Axis2 1.3. We should also do performance tuning before releasing 1.3. > > Azeez > > > On 5/15/07, Davanum Srinivas < [EMAIL PROTECTED]> 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] > > > > > > > > > > > > -- > > Davanum Srinivas :: http://davanum.wordpress.com > > > > > - > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Thanks > Afkham Azeez > > http://www.wso2.org > GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760 -- David Illsley - IBM Web Services Development - 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]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
xmlbeans is broken in the 1.2 release which is a show stopper for those with complicated schemas: https://issues.apache.org/jira/browse/AXIS2-2667 While 'edit the generated code to build the envelope' is a workaround, that's a bit much for new axis2 users and It'd be nice to see a quick release to fix it. I think the larger issue is our rc releases are not getting tested, allowing things like this to slip thru. Perhaps we need something like a 1.2 release, followed by a quick 1.2.1 , so the code actually gets used and the issues get flushed out. Robert On 5/16/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > Last time we did 1.1.1 due to two reason > 1- We found few critical issues with that AFAIK there wasn't even any critical blocking issues... 1.1.1 Release was mainly for the performance improvements..+few small bug fixes.. Thanks, Thilina -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
Last time we did 1.1.1 due to two reason 1- We found few critical issues with that AFAIK there wasn't even any critical blocking issues... 1.1.1 Release was mainly for the performance improvements..+few small bug fixes.. Thanks, Thilina -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
Hi All, Last time we did 1.1.1 due to two reason 1- We found few critical issues with that 2- We did performance improvements But this time I do not think that we are going to do performance improvements. Therefore I do not think we need to do a 1.2.1 and no need to follow the same fashion (I mean 1.1 -> 1.1.1 1.2 ->1.2.1) But we all like for 1.2.1 then I do not put -1 , and I will support that. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
I agree with Dennis that skipping 1.2.1 just because we can do a 1.3 is a bad idea. If there are a months worth of fixes for small problems on the branch lets release it and give our users something of a higher quality to use for the next few months. David On 16/05/07, Afkham Azeez <[EMAIL PROTECTED]> wrote: +1 for Axis2 1.3. We should also do performance tuning before releasing 1.3. Azeez On 5/15/07, Davanum Srinivas < [EMAIL PROTECTED]> 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] > > > > > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Afkham Azeez http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760 -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
+1 for Axis2 1.3. We should also do performance tuning before releasing 1.3. Azeez On 5/15/07, Davanum Srinivas <[EMAIL PROTECTED]> 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] > > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Afkham Azeez http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
Well Dims, how about https://issues.apache.org/jira/browse/AXIS2-2663... I do not think there are work arounds for that.. Anyway my requirement does not block skipping Axis2 1.2.1 as I'm already depending on the trunk... But there may be others who need proper class loading from the service archive.. I'm +1 for skipping 1.2.1 only if we are going to release 1.3 whiting another months time.. But with the new release process and the large amount of changes my guess is that the 1.3 would take at least another two months.. IMO we should not forget the unfortunate outcomes of not doing a quick 1.0.1after finding critical bugs with Axis2 1.0 , which gave lot of bad publicity for Axis2... Thanks, Thilina On 5/16/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: 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-
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
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? >>
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
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
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
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]
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
> 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. > I am big +1 on this . Other important thing is now the release process is bit different and we can not release all the dependent jar together like we did before ,so that simply tell that with that we will not be able to release Axis2 1.2.1 in one or two weeks. Therefore we need to wait few more weeks to get the release , in the meantime I did not find any BLOCKERS in 1.2 release for us to call for 1.2.1 . B'coz of that I am +1 on doing 1.3 release from the trunk and skipping 1.2.1. If we do so we can release 1.3 with clustering support . Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
