Hi Kent, I totally agree with you. We can specifically mention that it in some document (interop walkthrough??) and postpone to M2.
Any comments ? Regards, Shankar On Fri, May 1, 2009 at 6:22 AM, Kent Brown <[email protected]> wrote: > Thanks Shankar. I agree that we should be conservative about what bugs are > really required for M1. Things that make it difficult to > download/build/run, and things that violate any Apache principle that would > keep us from releasing should be M1. Anything else that can't be fixed > quickly should be postponed I think. For example, we have most of the > interop scenarios working and documented well. I think there is one > outstanding issue. If that isn't something that can be resolved quickly, it > seems it would be acceptable to make it part of the next release since there > are probably other WS-Security scenarios that should be covered in the next > release. > > Kent > > -----Original Message----- > From: Selvaratnam Uthaiyashankar [mailto:[email protected]] > Sent: Thursday, April 30, 2009 7:47 AM > To: [email protected] > Subject: Trial release pack > > Hi, > > I have packed and uploaded a trial release packages to [1]. Please try them > and send your comments. > > We still have 9 issues to be fixed for M1. Hope we can fix them ASAP, so > that we can proceed with the release. If any of them are not urgent for M1, > please mark it as M2. > > Regards, > Shankar > > [1] > http://people.apache.org/~shankar/stonehenge/m1/trialpack/<http://people.apache.org/%7Eshankar/stonehenge/m1/trialpack/> > > -- > S.Uthaiyashankar > Software Architect > WSO2 Inc. > http://wso2.com/ - "The Open Source SOA Company" > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
