Jeremy, The older release candidate jars in the Woden zip are a mistake. I can fix and rebuild, but based on your comments about IPMC it might be better to wait for the XmlSchema 1.3 release before starting any Woden M7a voting.
John. On 4/12/07, Jeremy Hughes <[EMAIL PROTECTED]> wrote:
Hi John, On 12/04/07, John Kaputin (gmail) <[EMAIL PROTECTED]> wrote: [...] > 2) XmlSchema 1.3, which will be released soon. In the meantime, M7a-RC1 is > dependent on XmlSchema 1.3 RC3. XmlSchema 1.3 RC2 is in the apache-woden-incubating-1.0M7a-RC1.zip as well as the RC3. Is this a mistake? Also, the axiom-api-1.2.3-RC1.jar is there as well as axiom-api-1.2.3.jar. I don't think the axiom RC1 jar is necessary. > > When XmlSchema 1.3 is release I will change the Woden M7a dependency to > XmlSchema 1.3 and rebuild the release files as M7a, then use these files for > the IPMC vote. In the meantime, I am initiating the Woden and WSPMC voting > on M7a-RC1. I believe the IPMC will only vote positively on the exact same files rolled for a woden-dev vote. They would probably be ok with woden-dev voting on files with RC1 in their name and then the files simply being renamed (not re-rolled) before the IPMC vote. So I think after the XmlSchema 1.3 release is done, and Woden M7a is rerolled, there needs to be a woden-dev vote, then an IPMC vote on the exact same files. If we're just talking about getting a build of Woden out that uses the latest possible release candidate of XmlSchema for Axis2 to test with, then I don't think we need to vote, after all that's really just another snapshot build. Cheers, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
