Hi Svante, On Wed, 8 Jan, 2025, 15:04 Svante Schubert, <[email protected]> wrote:
A new Xerces-J release is indeed great news! > To have Xerces-J's 2.12.3 release, someone needs to prepare RC from Xerces-J's sources from GitHub repos and have RC reviewed by subscribers of this list. I'm curious, whether other than me anyone else with Xerces repos's commit privileges might like to prepare Xerces-J's RC for next release? > We both desire the same for Xerces to always be high-quality, stable and > without regressions. > Definitely. The common practice to achieve this is automated regression tests - like > using GitHub functionality of automated builds and tests in the GitHub > cloud for every commit/PR. > This is true, while having GitHub as repos source. But for the next Xerces-J release I've a feeling that we can make a release without implementing this. A question definitely comes that, whether we should delay the next release for probably long time to implement and test this feature, or having a next release fairly quickly without having automated regression tests. To achieve this we must bring the tests and sources on the same branch. > With Xerces-J, the combined data size of Xerces-J's test sources and supporting files is very big, due to which IMHO I think this may not be a good approach. Also, doing this way shall require significant refactoring with how Xerces-J's test suite is structured, and I don't think large amounts of effort to do this is ok for the next release. -- Regards, Mukul Gandhi
