Thanks Fabian! All is good now. So, +1 from me too.

Best,
Suat

On Sat, Jan 26, 2013 at 12:46 PM, Fabian Christ <
[email protected]> wrote:

> Hi Suat,
>
> Thanks for checking. Did you import/update the used keys for this release
> prior to the check?
>
> The keys linked in the mail need to be imported in your local PGP
> environment.
>
> - Fabian
>
> *(Sent from my mobile. Sorry for typos.)
> Am 25.01.2013 13:37 schrieb "Suat Gönül" <[email protected]>:
>
> > Hi Fabian,
> >
> > I have a successful built, however when I ran the
> > "check_signatures_and_digests.sh" on the release zips, the pgp value
> seems
> > bad as follows:
> >
> >
> >
> .../158/org/apache/stanbol/apache-stanbol-entityhub/0.11.0/apache-stanbol-entityhub-0.11.0.pom
> > gpg:  BAD!!!!!!!!
> > md5 : GOOD (be8be9563c1889b22d135a7e3ee525aa)
> > sha1 : GOOD (d6c1f1ce68bba53b306e19b476daf17c30ead025)
> >
> > The other two are similar. Is there anything else that I should consider
> > here?
> >
> > Thanks a lot for your effort.
> >
> > Best,
> > Suat
> >
> >
> > On Wed, Jan 23, 2013 at 3:11 PM, Fabian Christ <[email protected]>
> wrote:
> >
> > > Hi,
> > >
> > > - signature and digests OK
> > > - build OK
> > > - dependencies OK
> > >
> > > +1
> > >
> > > 2013/1/23 Fabian Christ <[email protected]>:
> > > > Hi,
> > > >
> > > > first an important preparation step: In order to be able to build the
> > > > release artifacts you need to have the apache-stanbol-data-1.1.0
> > > > release locally installed in your system. Download the source release
> > > > from [1], unpack and install it with 'mvn install'. This step is
> > > > required since not all required data bundles are available via Maven
> > > > central.
> > > >
> > > > [1] http://stanbol.apache.org/downloads/
> > > >
> > > > This is a release vote for the following modules that need to be
> built
> > > > in the given order:
> > > >
> > > > 1) apache-stanbol-enhancer-0.10.0-source-release.[zip|tar.gz]
> > > > zip md5: 026f9906f0bbb74836ba86d94960127c
> > > > tar.gz md5: d9e7921d60d3c4254f1b978584ad7cd3
> > > >
> > > > -> install data-1.1.0 bundles
> > > >
> > > > 2) apache-stanbol-entityhub-0.11.0.[zip|tar.gz]
> > > > zip md5: 2e9ddae57cd15238fb77b043514a08aa
> > > > tar.gz md5: e3a1659133f3d4ddfde5fe4aaaa15907
> > > >
> > > > 3) apache-stanbol-contenthub-0.10.0.[zip|tar.gz]
> > > > zip md5: 3bf861c4afd0ef7ec9c309e483e52613
> > > > tar.gz md5: 7e482c990236bcb60ca0c77cd0b2c246
> > > >
> > > > The release source packages are staged in the dist SVN
> > > > https://dist.apache.org/repos/dist/dev/stanbol/158
> > > >
> > > > Keys are available at
> > > > http://www.apache.org/dist/stanbol/KEYS
> > > >
> > > > You can verify the release by checking out the source packages from
> > > > SVN. To verify checksums and keys use
> > > >
> > > > $  /releasing/check_signatures_and_digests.sh <path-to-packages>
> > > >
> > > > The release packages are also available via a staging repository that
> > > > additionally contains the generated binaries for Maven central:
> > > >
> > https://repository.apache.org/content/repositories/orgapachestanbol-158/
> > > >
> > > > The vote is open for at least 48 hours.
> > > >
> > > > Release Notes - Stanbol - Version enhancer-0.10.0
> > > >
> > > > ** 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
> > > >     * [STANBOL-633] - Extend the EnhancementStructure Ontology by the
> > > > fise:confidence-level property
> > > >     * [STANBOL-734] - ContentPart for NLP data - AnalyzedText
> > > >     * [STANBOL-823] - Refactor EntityLinkingEngine so that it does no
> > > > longer depend on the Stanbol Entityhub Component
> > > >     * [STANBOL-831] - EnhancementJobManger should correctly report if
> > > > the Execution of a Chain takes more than the max. configured time
> > > > ** Bug
> > > >     * [STANBOL-564] - Enhancer Engines README out of date
> > > >     * [STANBOL-614] - Enhancer returns inconsistent results
> > > >     * [STANBOL-617] - Define how TopicEnhancements are written to the
> > > > Enhancement Structure
> > > >     * [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
> > > >     * [STANBOL-651] - EventJobManager does not finish if an Engine
> > > > fails that is not the last Engine in the EnhancementChain
> > > >     * [STANBOL-671] - Felix console link is broken when deploying
> > > > Stanbol under a named context
> > > >     * [STANBOL-702] - Stanbol Enhacer ignores the 'uri' query
> parameter
> > > >     * [STANBOL-728] - NEREngineCore catches security exception and
> > > > rethrow them wrapped in an EngineException
> > > >     * [STANBOL-779] - EventJobManager may deadlock in case the
> > > > enhancement job is finished before the calling thread waits
> > > >     * [STANBOL-830] - EventJobManager does supports concurrent
> > > > enhancement of ContentItems with the same URI
> > > >     * [STANBOL-881] - (Re)add the String only Constructor to the
> PosTag
> > > class
> > > >     * [STANBOL-891] - hashCode method of MorphoFeatures throws NPE
> > > >     * [STANBOL-898] - The Stanbol Enhancer StreamSource
> > > > implementations MUST NOT close the parsed InputStream
> > > >     * [STANBOL-903] - NLPEngineHelper does not obtain wirte lock when
> > > > creating an AnalyzedText ContentPart in the initAnalyzedText utility
> > > > method
> > > > ** Improvement
> > > >     * [STANBOL-43] - Review service and HTTP APIs based on
> > > FISEapiReview20100331
> > > >     * [STANBOL-58] - Replace invented namespace names (j.0 and j.1)
> by
> > > > appropriate special prefixes
> > > >     * [STANBOL-171] - From dulcifier to enhancer.engines.refactor.
> > > >     * [STANBOL-369] - Set up a default "Accept" header or a more
> > > > comprehensive error message when "accept" is not set
> > > >     * [STANBOL-474] - Document or remove enhancer/query-rendering
> > > >     * [STANBOL-582] - Add support for EnhancementChains to the
> > > > Enhancer Benchmarking tool
> > > >     * [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
> > > >     * [STANBOL-780] - Make the enhancer releasable
> > > >     * [STANBOL-808] - Make it possible configure the
> > > > EventJobManagerImpl enhancement job timeout
> > > >     * [STANBOL-861] - Add support for country specific languages to
> > > > the LanguageConfig utility
> > > >     * [STANBOL-884] - Add ServiceLoader support for the
> > > ContentItemFactory
> > > >     * [STANBOL-904] - Move /enhancer/topic-web to
> > > /enhancement-engines/topic/web
> > > > ** New Feature
> > > >     * [STANBOL-105] - Support Multi-Site Scripting via Cross-Origin
> > > > Resource Sharing
> > > >     * [STANBOL-573] - Add Factory for ContentItems and Blobs
> > > >     * [STANBOL-574] - Add ContentItem/Blob implementation that stores
> > > > the parsed content in a temporary file
> > > >     * [STANBOL-583] - CELI enhancement engine(s)  - Contribution to
> > > stanbol
> > > >     * [STANBOL-878] - Add serialization support to the AnalyzedText
> > > ContentPart
> > > > ** Question
> > > >     * [STANBOL-506] - Delete deprecated TaxonomyLinkingEngine from
> SVN?
> > > > ** Task
> > > >     * [STANBOL-885] - Let UIMA local template use latest UIMA SDK and
> > > > Lucene analyzers
> > > >     * [STANBOL-900] - Release enhancer-0.10.0
> > > > ** Test
> > > >     * [STANBOL-575] - Create a test module for the Stanbol Enahncer
> > > >     * [STANBOL-612] - Add helper for validating the Stanbol
> > > > EnhancementStructure to the Enhancer test module
> > > >     * [STANBOL-759] - Add utility to the enhancer.test module for
> > > > checking if RemoteServices are currently unavailable
> > > >     * [STANBOL-766] - fise:EntityAnnotations may be also related to
> > > > other EntityAnnotations
> > > >
> > > >
> > > > Release Notes - Stanbol - Version entityhub-0.11.0
> > > >
> > > > ** Sub-task
> > > >     * [STANBOL-776] - remove dependency of entityhub.model.clerezza
> to
> > > > entityhub.core
> > > > ** Bug
> > > >     * [STANBOL-661] - LDPath implementation of the Entityhub MUST NOT
> > > > throw IllegalArgumentExceptions on failed type conversions
> > > >     * [STANBOL-668] - Loading of Namespace prefixes in the SolrYard
> > > > implementation is not thread save
> > > >     * [STANBOL-669] - Property <-> Field cache of the SolrYard is not
> > > > syncronized
> > > >     * [STANBOL-676] - ClerezzaYard create/update operation may store
> > > > more data as intended
> > > >     * [STANBOL-678] - SolrYard needs to quote search terms like "OR"
> > > "AND" "NOT"
> > > >     * [STANBOL-697] - invalid SPARQL query
> > > > (org.apache.stanbol.enhancer.servicesapi.ChainException: Enhancement
> > > > Chain failed because of required Engine 'dbpediaLinking' failed with
> > > > Message: Unable to process ContentItem)
> > > >     * [STANBOL-727] - Generic types is not correctly validated in
> > > > RepresentationReader#isReadable
> > > >     * [STANBOL-777] - Update pom.xml files of the Entityhub to NOT
> > > > include unecessary transitive dependencies
> > > >     * [STANBOL-829] - Entityhub SiteMaanger does not forward Entity
> > > > dereferenceing requests to Sites that define an NULL or empty Prefix
> > > > ** Improvement
> > > >     * [STANBOL-662] - Add configuration option for the Graph URI used
> > > > by the ClerezzaYard
> > > >     * [STANBOL-663] - Allow ClerezzaYard to work with Clerezza Graphs
> > > > (read-only RDF graphs)
> > > >     * [STANBOL-794] - Add support for filtering/including Entities
> > > > with no value for the configured Field to the FieldValueFilter
> > > > (EntityProcessor)
> > > >     * [STANBOL-816] - Logs of SolrQueryFactory to verbose
> > > >     * [STANBOL-870] - The ResourceLoader utility of the
> > > > EntityhubIndexingTool should support the copying of imported files to
> > > > a configured folder
> > > > ** New Feature
> > > >     * [STANBOL-665] - Adding removeAll functionality to the Entityhub
> > > >     * [STANBOL-677] - ClerezzaYard instances should expose their RDF
> > > > graph via the Stanbol SPARQL endpoint
> > > >     * [STANBOL-764] - Add support for importing Quads to the JenaTDB
> > > > indexing source
> > > > ** Question
> > > >     * [STANBOL-804] - Creating a spanish Index
> > > > ** Task
> > > >     * [STANBOL-901] - Release entityhub-0.11.0
> > > > ** Test
> > > >     * [STANBOL-62] - Complete unit test framework for Entityhub
> > > >
> > > >
> > > > Release Notes - Stanbol - Version contenthub-0.10.0
> > > >
> > > > ** Sub-task
> > > >     * [STANBOL-701] - Divide Contenthub servicesapi module into
> > > > separate modules as: Contenthub specific and common api
> > > >     * [STANBOL-785] - Change REST service consuming multipart data
> > > > with the one taking ContentItem parameter directly
> > > >     * [STANBOL-786] - Remove constraint parameter while creating
> > > > ContentItem through RESTful services
> > > >     * [STANBOL-787] - Remove SolrContentItemImpl since it was only
> > > > used for specifying constraints for the ContentItem
> > > >     * [STANBOL-788] - Remove update services from StoreResource
> > > > ** Bug
> > > >     * [STANBOL-424] - SPARQL queries using FROM/FROM NAMED do not
> work
> > > > as expected
> > > >     * [STANBOL-546] - Can't download items in Contenthub webinterface
> > > > inserted via cms-adapter
> > > >     * [STANBOL-580] - Remove Dependency for
> > > > "stanbol.commons.web.sparql" to "stanbol.contenthub.servicesapi"
> > > >     * [STANBOL-581] - When a content item is deleted or updated its
> > > > enhancements are not updated in the enhancement graph
> > > >     * [STANBOL-693] - Add delete method for the CORS support while
> > > > deleting an LDPath program from Contenthub
> > > >     * [STANBOL-694] - Return 404 instead of 200 if the target object
> > > > does not exist while deleting a content item or LDPath program
> > > >     * [STANBOL-731] - Enhancement Graph is not registered properly to
> > > > the OSGi environment
> > > >     * [STANBOL-782] - Do not throw StoreException when a ContentItem
> > > > does not have textual content
> > > >     * [STANBOL-833] - Feedbacks on SolrStoreImpl
> > > > ** Improvement
> > > >     * [STANBOL-584] - Provide an easy to use, Solr independent way to
> > > > benefit from faceted search
> > > >     * [STANBOL-781] - Execute LDPath on RDF based parts of
> ContentItems
> > > >     * [STANBOL-783] - Add option to specify chain name while
> > > > submitting content items to Contenthub
> > > >     * [STANBOL-784] - Use Multipart serialization of ContentItem in
> > > > Contenthub while content creation
> > > >     * [STANBOL-840] - Improve the parameter and response types;
> > > > parameter validation of REST services of Contenthub
> > > > ** Task
> > > >     * [STANBOL-799] - Make Contenthub releaseable
> > > >     * [STANBOL-902] - Release contenthub-0.10.0
> > >
> >
>

Reply via email to