Hi, On Mon, Nov 20, 2017 at 10:54 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
> On Sun, Nov 19, 2017 at 3:08 PM, Sergio Fernández <wik...@apache.org> > wrote: > > Apache Commons RDF 0.5.0 RC2 is available for review at (r23205): > > > > https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co > > mmons-rdf-0.5.0-RC2/ > > The current rev for this link is 23215, are you sure 23205 is correct? > And currently it's 23217 for me. But that doesn't mean much. I'm pretty sure I did push the release on that revision: $ svn log -l 1 https://dist.apache.org/repos/dist/dev/commons/rdf/apache-commons-rdf-0.5.0-RC2/ ------------------------------------------------------------------------ r23205 | wikier | 2017-11-19 13:54:15 -0800 (Sun, 19 Nov 2017) | 1 line added correct source release for apache commons rdf 0.5.0 RC2 ------------------------------------------------------------------------ So rev. 23205 is still correct. Subversion handles revisions at a global level. So the checked out revision will always be '>=', '=' only when no changes in the overall repository, not just in the subpath. > This source release produces the following binary artifacts: > > > > commons-rdf-parent-0.5.0 > > commons-rdf-api-0.5.0 > > commons-rdf-simple-0.5.0 > > commons-rdf-jena-0.5.0 > > commons-rdf-rdf4j-0.5.0 > > commons-rdf-jsonld-java-0.5.0 > > commons-rdf-integration-tests-0.5.0 > > You should include the checksums from the email you received from Nexus. > I read that Commons policy. The issues is that I didn't get that email, and I couldn't find how to easily gather those checksums given the amount of binary artifacts this source release produces. Since I only called to vote the source artifact, I understood the binaries aren't being actually voted, that's why I didn't dig deeper. But I'm happy to provide those if someone point me how to gather those checksums from Nexus. Cheers,
