Hi John, On Mon, May 2, 2022 at 11:01 PM JOHN Morris <j.morri...@ntlworld.com> wrote: > Is it to be assumed that a new release will have been exercised with all the > previous test-cases, in order to verify that no past issues (that were > resolved in previous releases) are being re-introduced in the new release?
We've a very good collection of test cases, that we run before making a new XercesJ release. This ensures that, no past issues resolved in the previous releases are being re-introduced in the new release. Generally, the newer XercesJ release is better than the previous release, due to improved implementation and/or new bug fixes. > Also, I assume that the as-yet-unresolved issues from earlier releases (e.g. > 2.12.2, in this case) are each mainly characterised by a certain set of > symptoms. Do those symptoms normally remain stable, across releases, or is it > the responsibility of the originator of the issue report(s) to try to > replicate their issue(s) under the new release and to understand what new > symptoms relate to that/those issue(s).? Generally, any unresolved issues from earlier releases, remain stable with the newer releases. While making a new XercesJ release, firstly we publish a release candidate (RC) for review and vote by community. After the RC is through with the voting process, we push the RC to production. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org
