Hi Gary & all, Apologies for the confusion, during the previous mail about this subject.
Below mentioned is the, newly corrected information about the XalanJ 2.7.3 RC that needs to be reviewed now. We've published the new RC for XalanJ 2.7.3 release (located at https://dist.apache.org/repos/dist/dev/xalan/j/2.7.3/RC5/). This RC, incorporates review comments provided for the previous RC. The necessary XalanJ build tests pass, with this RC. Details of changes since XalanJ version 2.7.2 are mentioned within the release notes (that can be seen, within the documentation in the archives xalan-j_2_7_3-bin.zip & xalan-j_2_7_3-bin.tar.gz). The signed tag associated with this RC, is located at https://gitbox.apache.org/repos/asf?p=xalan-java.git;a=tags (tag name xalan-j_2_7_2-rc5. signing key used is 7B2586A6B5E25C3D) The latest KEYS file is located at: https://github.com/apache/xalan-java/blob/xalan-j_2_7_1_maint/KEYS Please review this release candidate and vote. [ ] +1 Release these artifacts [ ] +0 OK, but... [ ] -0 OK, but really should fix... [ ] -1 I oppose this release because... Great work everyone. Here's my +1 for this RC. On Sat, Oct 15, 2022 at 11:41 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > This is SO confusing. There already was an RC1 that was voted down, right? > The next RC should be... what? RC4 or 5, the subject of the email should have > the RC# so we can keep track. > > Gary > > > On Sat, Oct 15, 2022, 12:58 Mukul Gandhi <muk...@apache.org> wrote: >> >> Hi Gary & all, >> We've published the new RC for XalanJ 2.7.3 release (located at >> https://dist.apache.org/repos/dist/dev/xalan/j/2.7.3/RC1/). This RC, >> incorporates review comments provided for the previous RC. >> >> The necessary XalanJ build tests pass, with this RC. >> >> Details of changes since XalanJ version 2.7.2 are mentioned within the >> release notes (that can be seen, within the documentation in the >> archives xalan-j_2_7_3-bin.zip & xalan-j_2_7_3-bin.tar.gz). >> >> The signed tag associated with this RC, is located at >> https://gitbox.apache.org/repos/asf?p=xalan-java.git;a=tags (tag name >> xalan-j_2_7_3-rc1. signing key used is 7B2586A6B5E25C3D) >> >> The latest KEYS file is located at: >> https://github.com/apache/xalan-java/blob/xalan-j_2_7_1_maint/KEYS >> >> Please review this release candidate and vote. >> >> [ ] +1 Release these artifacts >> [ ] +0 OK, but... >> [ ] -0 OK, but really should fix... >> [ ] -1 I oppose this release because... >> >> Great work everyone. Here's my +1 for this RC. >> >> On Sat, Oct 15, 2022 at 6:26 PM Gary Gregory <garydgreg...@gmail.com> wrote: >> > >> > More importantly, each RC should have a signed tag [1] in git and that >> > tag should be in the VOTE email to help keep a record and connect the >> > dots. >> > >> > Once a release is successful, a new signed tag with the "rel/" prefix >> > should be created, this tag will be read-only automatically if the >> > GitBox repository is properly set up. The "rel/" convention is not in >> > the current repo because IIRC we've only adopted it since we moved to >> > git. >> > >> > Gary >> > >> > [1] https://gitbox.apache.org/repos/asf?p=xalan-java.git;a=tags >> > >> > On Sat, Oct 15, 2022 at 8:51 AM Gary Gregory <garydgreg...@gmail.com> >> > wrote: >> > > >> > > Note that, IMO, https://dist.apache.org/repos/dist/dev/xalan/j/2.7.3/ >> > > should not contain the old RCs, it could lead to testing an incorrect >> > > RC by accident. >> > > >> > > Gary >> > > >> > > On Sat, Oct 15, 2022 at 8:49 AM Gary Gregory <garydgreg...@gmail.com> >> > > wrote: >> > > > >> > > > When I unzip the src zip and run "ant fulldist", I get: >> > > > >> > > > BUILD FAILED >> > > > /Users/garydgregory/rc/xalan-j_2_7_3/build.xml:1415: The following >> > > > error occurred while executing this line: >> > > > /Users/garydgregory/rc/xalan-j_2_7_3/build.xml:1347: Warning: Could >> > > > not find file >> > > > /Users/garydgregory/rc/xalan-j_2_7_3/lib/endorsed/xml-apis.jar >> > > > to copy. >> > > > >> > > > Total time: 37 seconds >> > > > >> > > > Gary -- Regards, Mukul Gandhi
