+1 (binding)

The checksums and signatures are all good
I was able to build from the git tag and the source distribution
LICENSE and NOTICE files look good
I have tested the release successfully in downstream projects

Thank you, Andy!


On Thu, Apr 20, 2023 at 9:57 PM Bruno Kinoshita <ki...@apache.org> wrote:

> +1 and I confirm the tests are now all passing on my environment
>
> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> Maven home: /opt/apache-maven-3.8.5
> Java version: 17.0.6, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-70-generic", arch: "amd64", family:
> "unix"
>
> Thank you Andy!
>
>
> On Thu, 20 Apr 2023 at 11:27, Andy Seaborne <a...@apache.org> wrote:
>
> > Hi,
> >
> > Here is a vote on the release of Apache Jena 4.8.0.
> > This is the second release candidate.
> >
> > The deadline is
> >
> >      Sunday, 23rd April 2023 at 12:00 UTC
> >
> > Please vote to approve this release:
> >
> >          [ ] +1 Approve the release
> >          [ ]  0 Don't care
> >          [ ] -1 Don't release, because ...
> >
> > ==== Items in this release
> >
> > == RC 2
> >
> > a/ Fix the initialization issue found in RC1
> > https://github.com/apache/jena/pull/1847
> >
> > b/ GH-1749: Replacing webpack chunks by Vite rollup
> >
> > c/ fix and test for JENA-2352
> >
> > == RC 1
> >
> > https://s.apache.org/jena-4.8.0-issues
> >
> > * The RDF/XML parser has been converted to use the
> >    Jena IRI abstraction IRIx.
> >    https://github.com/apache/jena/issues/1773
> >
> > This is the first part of a move to convert the RDF/XML parser to be
> > consistent with the rest of Jena parsing
> >
> > 1. unified IRI treatment of error handling and reporting throughout Jena
> > 2. improve maintainability
> > 3. allow for alternative providers of IRI functionality
> >
> > * Add CHANGES.txt
> > https://github.com/apache/jena/blob/main/CHANGES.txt
> >    It has been backfilled with announcement message from 4.0.0 onwards.
> >    It will be updated after the release - it has a link to [ANN]
> >
> > * Search facility on the Jena website
> >
> > @lucasvr (Lucas C. Villa Real) provided an analysis and improvement to
> > bulk loading operations.
> >    https://github.com/apache/jena/issues/1803
> >    https://github.com/apache/jena/pull/1819
> >
> > @wjl110 - Shiro upgrade PR#1728
> >    https://github.com/apache/jena/pull/1728
> >
> > Lucene upgrade from 9.4.2 to 9.5.0
> >    https://github.com/apache/jena/pull/1740
> >    https://lists.apache.org/thread/696xgpyg2441kzdowmp1b40tshctw25c
> >
> > @dplagge (Daniel Plagge) - Delta graph fix
> > https://github.com/apache/jena/issue/1751
> >
> > SimonBin: Fix for sharing link in Fuseki and YASGE
> >    https://github.com/apache/jena/issues/1745
> >
> > Improved performance of "GRAPH ?g {}" (all graph names)
> > Prefix scan -- GRAPH ?G
> >    https://github.com/apache/jena/issues/1639
> >    https://github.com/apache/jena/pull/1655
> >
> > @nichtich (Jakob Voß) jena-site improvements:
> >    https://github.com/apache/jena-site/pull/151
> >
> > @sverholen JENA-2350 Pass JsonLdOptions to titanium for json-ld 1.1
> >
> > ==== Release Vote
> >
> > Everyone, not just committers, is invited to test and vote.
> > Please download and test the proposed release.
> >
> > Staging repository:
> >    https://repository.apache.org/content/repositories/orgapachejena-1058
> >
> > Proposed dist/ area:
> >    https://dist.apache.org/repos/dist/dev/jena/
> >
> > Keys:
> >    https://svn.apache.org/repos/asf/jena/dist/KEYS
> >
> > Git commit (browser URL):
> >    https://github.com/apache/jena/commit/198e6950c7
> >
> > Git Commit Hash:
> >    198e6950c7652ffe68c9171bc5ed92c69210c60a
> >
> > Git Commit Tag:
> >    jena-4.8.0
> >
> > This vote will be open until at least
> >
> >    Sunday, 23rd April 2023 at 12:00 UTC
> >
> > If you expect to check the release but the time limit does not work
> > for you, please email within the schedule above.
> >
> >      Thanks,
> >      Andy
> >
> > Checking:
> >
> > + are the GPG signatures fine?
> > + are the checksums correct?
> > + is there a source archive?
> > + can the source archive be built?
> >            (NB This requires a "mvn install" first time)
> > + is there a correct LICENSE and NOTICE file in each artifact
> >            (both source and binary artifacts)?
> > + does the NOTICE file contain all necessary attributions?
> > + have any licenses of dependencies changed due to upgrades?
> >             if so have LICENSE and NOTICE been upgraded appropriately?
> > + does the tag/commit in the SCM contain reproducible sources?
> >
>

Reply via email to