Dear Stanbolers,
please vote for releasing Apache Stanbol 0.10.0-incubating (RC3).
In the last RC2 the DISCLAIMER files were missing. This was fixed for RC3.
This release consists of the following components fixing the listed
issues. When verifying the release, you have to build the components
in the given order because of dependencies.
- source-assembly-0.10.0-incubating-source-release.zip
MD5 8ce4336700b3967c210f406f0dcc618e
fixed issues:
* [STANBOL-645] - Rename source release assembly descriptor
* [STANBOL-640] - Create Stanbol source release assembly descriptor
- stanbol-parent-1-incubating-source-release.zip
MD5 19d29a59b3e1eb324feb0f2ba5b8be27
fixed issues:
* [STANBOL-553] - Remove dependency management for
org.apache.stanbol components from parent POM
* [STANBOL-666] - Missing DISCLAIMER file in artifacts
- org.apache.stanbol.commons.solr.core-0.10.0-incubating-source-release.zip
MD5 e5a51b7df302896203b590d2dbf6841c
fixed issues:
* [STANBOL-606] - Language prefixes are added to non
TextConstraint in queries for the Entityhub
- org.apache.stanbol.commons.web.base-0.10.0-incubating-source-release.zip
MD5 c2d5ca5bf5c058577a38453a48e89376
fixed issues:
* [STANBOL-555] - Remove test dependency of commons.web.base to
enhancer.servicesapi
* [STANBOL-606] - Language prefixes are added to non
TextConstraint in queries for the Entityhub
* [STANBOL-607] - SolrYard should use quotes instead of AND for
multi word TextConstraints
- org.apache.stanbol.data.parent-0.10.0-incubating-source-release.zip
MD5 3134e99eb72f3bb0bf5ea46e9c2d627f
fixed issues:
* [STANBOL-637] - Build warns for downloaded OpenNLP models when
instead a DBPedia index is downloaded
- org.apache.stanbol.data.sites.dbpedia-1.0.4-incubating-source-release.zip
MD5 e66249489c978e8305f68340c337890b
fixed issues:
* [STANBOL-638] - Make DBPedia data bundle releaseable
- apache-stanbol-entityhub-0.10.0-incubating-source-release.zip
MD5 1741c62f4850d5c3b00a962112c6a2dd
fixed issues:
* [STANBOL-590] - LDPath processor operating on the IndexingSource
and Implementation for the JenaTDB based indexing source.
* [STANBOL-592] - LDPath processor operating on the
IndexingDestination in the post-processing phase
* [STANBOL-598] - Support Reconciliation properties on the full
text field of entities
* [STANBOL-599] - Support Reconcilliation properties on the semantic context
* [STANBOL-568] - Entityhub indexing tool is not able to
initialise if the path contains a space
* [STANBOL-606] - Language prefixes are added to non
TextConstraint in queries for the Entityhub
* [STANBOL-610] - Indexing Directory parameter does not work for
the genericrdf Indexing Tool
* [STANBOL-616] - Wrong CORS Response
* [STANBOL-654] - The SolrYard does not correcly enclose multi
word query terms in quotes
* [STANBOL-589] - Allow usage of SimilarityConstraints via the
RESTful API of the Entityhub
* [STANBOL-595] - Add support for ValueConstraints with multiple values
* [STANBOL-600] - Update the namespaces used by the Entityhub to
stanbol.apache.org URIs
* [STANBOL-607] - SolrYard should use quotes instead of AND for
multi word TextConstraints
* [STANBOL-556] - LdPath processor for Entityhub Indexing
* [STANBOL-591] - Add support for post-processing to the Entityhub
Indexing Tool
* [STANBOL-593] - EntityIterator implementation based on Jena TDB
that allows to filter Entities based on Triple Filters
* [STANBOL-594] - Google Refine Reconciliation Service support
* [STANBOL-596] - Add support for full text searches to FieldQuery
* [STANBOL-597] - Add support for semantic context queries to FieldQuery
The released artifacts can be downloaded from the staging repository:
https://repository.apache.org/content/repositories/orgapachestanbol-257
Keys are at:
http://www.apache.org/dist/incubator/stanbol/KEYS
Please note, that the staging repository also contains additional
Maven artifacts and binaries of the Entityhub (and of the other
components). However, the source release of the Entityhub is located
in the 'apache-stanbol-entityhub-0.10.0-incubating' folder. The Maven
artifacts and binaries are only deployed for convenience and were
automatically created from the source release. The source release
packages to verify are always named '*.source-release.[zip|tar.gz]'.
To check and verify the release, you can use two utility scripts that are
available in the SVN trunk.
Usage:
$ check_staged_release.sh 257 /tmp
$ check_release_matches_tag.sh 257 /tmp
This vote is open for at least 72 hours.
--
Fabian
http://twitter.com/fctwitt
