Hi Reto all,
On Wed, Apr 23, 2014 at 8:53 AM, Reto Gmür <r...@apache.org> wrote:
> Hello,
>
> The 1.0 trunk has been quite stable recently. In the fusepool [1] project
> we have been using it successfully for a while. I think we could release
> what we have.
Thats also because I had not so much time to work on the things that
would bring major changes ....
IMO before the first 1.0 release we need to address all major changes
that will break backward compatibility. From my side this would
include
* Changes to the Enhancer API as suggested by STANBOL-1326 (see also
my mail from yesterday [1])
* Review/Change the Stanbol Enhancement Structure
* with a look at standards like Open Annotation and NIF
* and especially considering typical use cases
In addition there is still an open discussion about the Contenthub and
the CMS Adapter component. AFAIK @Rafa was investigating this. Could
someone provide more information on that.
If we want to have an early release of the trunk version we could
consider to define milestone releases and assign the JIRA issues
accordingly. Not sure how such releases would play together with the
semantic versioning rules of OSGI.
BTW: I am currently working on the 0.12.1 release. As part of that I
have updated most of the OSGI, Sling and commonly used dependencies
(both for 0.12 and in trunk).
As part of this work I also noticed the huge number of dependencies of
Jersey 2 in the trunk. With the update from 2.2 to 2.7 three
additional one where added (including a repacked version of Google
Guava with several MByte). @Reto: Does we still depend on using
jersey, or could we also consider other options for JAX-RS with 1.0
best
Rupert
[1] http://stanbol.markmail.org/thread/beexsyf2t62lavqz
>
> WDYT?
>
> Cheers,
> Reto
>
>
> 1. https://github.com/fusepool
--
| Rupert Westenthaler rupert.westentha...@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
| REDLINK.CO
..........................................................................
| http://redlink.co/
