I find the Xerces release process to be confusing, but I think I've pieced together some things. Please let me know where I'm incorrect:
1) Michael Glavassevich is the project lead and dictates how and when Xerces is released. 2) Xerces has two separate code bases, "trunk" and "xml-schema-1.1-beta". These are released as separate JARs and have a different set of bugs, features, and fixes. 3) Whenever Xerces is released, both the "trunk" and "xml-schema-1.1-beta" are released with the same version number. 4) All of your (Muluk's) fixes were made in "xml-schema-1.1-beta" and so would be included in any Xerces release, but would go into the "xml-schema-1.1-beta" JAR, not the mainline Xerces JAR. To get your fixes into the mainline release, the xml-schema-1.1-beta branch would need to be merged into trunk, but there are no near-term plans to do this. Is this correct? Muluk Gandhi wrote: > I've just now mentioned within various Xerces Jira issues that I had earlier > fixed raised against 2.11.0 release, that the fixes for them will be > available in the 2.12.0 release. When I tagged the issues in JIRA, I had carefully checked where each fix was committed so that the auto-generated release notes[1] wouldn't include fixes that aren't in the mainline version, which is what people will download when they download 2.12.0. As a Xerces user, I find it confusing to see release notes that say something is "fixed" in version 2.12.0 when it's not fixed in the version that I download, but in a completely different JAR called "xml-schema-1.1-beta" that's built from a different code base. Since there are really two different libraries released, I think it'd be clearer to have two version labels in JIRA, something like "2.12.0" and "2.12.0 Schema 1.1 beta". I'm willing to retag the JIRA tickets if you approve of this suggestion, but I think I'd need Michael's approval, too. That said, since I'm not a Xerces developer and I have no problem with you following whatever process you like. Muluk Gandhi wrote: > I felt that, the various fixes that I've now marked as releasing for 2.12.0, > that were fixed by me must also go into the 2.12.0 release. Are you suggesting that the schema 1.1 branch gets merged back into the mainline code? I think that would be great. Not only would get important fixes into the mainline release, but it would clear up a lot of confusion that I've seen on the mailing lists, including the recent confusion where someone claims that Xerces doesn't pass schema 1.1 W3C unit tests and you claim it does (I assume that he was looking at trunk and you were looking at the xml-schema-1.1-dev branch). [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10520&version=12336542 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
