Hi,
I had a look at the resolved issues since 0.9.0-incubating in Jira and
the Enhancer got some improvements which are IMO ready for release.
** Sub-task
* [STANBOL-459] - Implement cross validated evaluation of the
classifier with Precision / Recall and F1 score for each topic in the
model
* [STANBOL-576] - Move tests/implementations from the Enhancer
Services API module to avoid cyclic dependencies
* [STANBOL-577] - Add Interfaces for parsing Content
* [STANBOL-579] - Allow streaming of transformed content to Blobs
* [STANBOL-613] - Define a standard way on how to obtain the
extracted language
** Bug
* [STANBOL-564] - Enhancer Engines README out of date
* [STANBOL-622] - The KeywordLinkingEngine should check if all
Tokens of a Label match against the text
* [STANBOL-623] - The KeywordLinkingEngine does not select the
best fitting label for suggested Entities
* [STANBOL-624] - The NamedEntityTagging engine should use
confidence values between [0..1]
* [STANBOL-625] - EnhancementEngines that suggest Entities from
the Stanbol Entityhub should add the name of the ReferencedSite
* [STANBOL-634] - EventJobManager does not correctly set the
Status of the EnhancementChain to failed if a required
EnhancementEngine fails
* [STANBOL-636] - KeywordLinkingEngine should report a
EngineException instead of a IllegalStateException if the configured
ReferencedSite is not available
** Improvement
* [STANBOL-474] - Document or remove enhancer/query-rendering
* [STANBOL-627] - Update to Tika 1.1
* [STANBOL-630] - Confidence values MUST BE in the range [0..1]
* [STANBOL-635] - Web UI of the Stanbol Enhancer should show
information about failed Engines and print the Stacktrace in case of a
failed Exection of an Enhancement Chain
** New Feature
* [STANBOL-573] - Add Factory for ContentItems and Blobs
* [STANBOL-574] - Add ContentItem/Blob implementation that stores
the parsed content in a temporary file
** Question
* [STANBOL-506] - Delete deprecated TaxonomyLinkingEngine from SVN?
** Test
* [STANBOL-575] - Create a test module for the Stanbol Enahncer
I have also analyzed the involved SNAPSHOT artifacts. This would be
the list of to be released artifacts:
org.apache.stanbol.enhancer.parent:pom:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.test:jar:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.core:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.test:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.rdfentities:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.core:jar:0.10.0-incubating-SNAPSHOT:test
org.apache.stanbol.enhancer.test:jar:0.10.0-incubating-SNAPSHOT:test
org.apache.stanbol.enhancer.weightedjobmanager:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.eventjobmanager:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.jobmanager.reactor:pom:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.chain.allactive:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.chain.graph:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.chain.weighted:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.chain.list:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.jersey:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.core:jar:0.10.0-incubating-SNAPSHOT:test
org.apache.stanbol.enhancer.test:jar:0.10.0-incubating-SNAPSHOT:test
org.apache.stanbol.enhancer.ldpath:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.core:jar:0.10.0-incubating-SNAPSHOT:test
org.apache.stanbol.enhancer.test:jar:0.10.0-incubating-SNAPSHOT:test
org.apache.stanbol.enhancer.benchmark:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-incubating-SNAPSHOT:compile
org.apache.stanbol.enhancer.defaults:bundle:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.bundlelist:partialbundlelist:0.10.0-incubating-SNAPSHOT
org.apache.stanbol.enhancer.reactor:pom:0.10.0-incubating-SNAPSHOT
But before we can release the Enhancer we need a stable parent POM,
too. So we would have to release the Stanbol parent, additionally.
** Improvement
* [STANBOL-553] - Remove dependency management for
org.apache.stanbol components from parent POM
** Task
* [STANBOL-552] - Specify next Stanbol release number
Artifact:
org.apache.stanbol.stanbol-parent:pom:0.10.0-incubating-SNAPSHOT
For the parent POM I would like to change the versioning schema like
other projects do this. The release version of the parent POM would be
"1" and the next development version would be changed to "2-SNAPSHOT".
I think most projects use this style as there is no need for minor or
revisions in the parent POM. Also, the parent POM should not change
that often.
Are there any pending changes in these artifacts that I should wait
for before making the release? Then please raise a flag.
I would like to prepare the release tomorrow morning.
Best,
- Fabian
--
Fabian
http://twitter.com/fctwitt
