Hi Mukul, A new Xerces-J release is indeed great news!
We both desire the same for Xerces to always be high-quality, stable and without regressions. 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. To achieve this we must bring the tests and sources on the same branch. Would you agree with the above so far? In case you lack any kind of information or something is/was not well explained by myself - please let me know! What are your thoughts, your view of the pros/cons of this suggestion? Kind regards, Svante On Sat, 4 Jan 2025 at 16:48, Mukul Gandhi <gandhi.mu...@gmail.com> wrote: > Hi Svante, > I've been thinking of proposing making a new Xerces-J release. > There are various new code changes on Xerces-J's repos, that I think > are important enough for having a new Xerces-J release. > > Xalan-J's XSL 3 latest code also requires the new Xerces-J release. > > I'm really not sure how to go about adding the GitHub regression test > that you've mentioned within your mail below. > > On Sat, Jan 4, 2025 at 5:25 PM Svante Schubert > <svante.schub...@gmail.com> wrote: > > > > Hello Mukul, > > > > Thanks for your contribution. > > > > What is your plan to bring all these branches together? > > In general, we should avoid duplicated data, right? > > > > Kind regards, > > Svante > > > > PS: I asked about the Xerces tests some months ago. We should add a > GitHub regression test that always runs after every commit and stays green > - I could not reproduce green tests for the last release. > > > -- > Regards, > Mukul Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-dev-h...@xerces.apache.org > >
