Hi Rafa There was a delay between the discussion on the list and me committing the changes. The reason is also that some little issues had to be fixed in clerezza so that all of Stanbol works.
But the problem is not the change between earlier SNAPSHOT version and the release but the lack of release. Developing against a SNAPSHOT version should be the exception, the whole apache release and licensing process depends on artifacts actually being released if people just rely on the subversion code rather than releases this misses a very important aspect of the Apache way and licensing. So the problem is that we're not releasing. When an issue is fixed it should never take so long till the fix is available to the public, that is, till there is a release. Cheers, Reto On Wed, 15 Jun 2016, at 12:32, Rafa Haro wrote: > Hi all, > > We should get back to the releasing discussion as soon as possible. > Yesterday, I had to adapt the code of several custom engines that we used > for an internal project in my company because I was relying on version > 1.0.0-SNAPSHOT and like a month ago Clerezza version was updated. This is > not nice, because probably there are more people out there developing > with > 1.0.0-SNAPSHOT artifacts (because those are the only ones that we can get > using maven if you want to use "version 1.x") which code is not going now > to compile at all like it happened to me yesterday. > > I'm not saying that the update to the new Clerezza API shouldn't have > been > done and released as SNAPSHOT version, but I would have expected at least > to announce it here first and to wait until releasing and publish a first > 1.0.0 version for people that have been working with 1.0.0-SNAPSHOT prior > to this major change doesn't seen his code affected. > > Anyway, Fabian, could we speed up the handover for the releasing process? > > By the way, I have updated Clerezza bundlelists dependencies for all the > launchers, because only the full launchers was updated in the last commit > > Cheers, > Rafa
