Re: Commit window for 0.x release in trunk closes this Friday

Hi Reto, +1. I just was reviewing my remaining tasks. Agree it is not critical. Cheers, Rafa El viernes, 18 de octubre de 2013, Reto Bachmann-Gmür escribió: > Hi Rafa, all, > > I think adding Unit Test is certainly not a release critical bugfix. The > incompatibilities between entityhub compone

Re: Commit window for 0.x release in trunk closes this Friday

Hi Rafa, all, I think adding Unit Test is certainly not a release critical bugfix. The incompatibilities between entityhub components I mentioned before [1] seems to me more likely to be release critical. However this could I think as well be addressed in a release branch while the main developmen

Re: Commit window for 0.x release in trunk closes this Friday

Hi, @Fabian: I couldn't exactly say. It is being a complicated month but eventually, if the next week won't get complicated, it would be possible. @Reto: sorry, I directly commented it to Rupert via chat. I need to write unit tests for STANBOL-1125. I can't remember right now but I would say I al

Re: Commit window for 0.x release in trunk closes this Friday

Hi, Having just been spending hours after merging down some cahnges to ng branch I would really advocate not adding any stuff unless urgent bug fixes. 0.12-SNAPSHOT versions have been used and thus tested for quite a while now. let's relase this time proven code rather than pushing in features. @

clerezza yard doesn't compile against current entityhub

Hi, I merged down the latest changes from entityhub to the ng branch (locall for now) and I'm encountering compilation issues. After hours of trying to find out what went wrong with merge and cursing svn I found out that I was looking in the wrong place. The clerezza solr yard doesn't compile us

Build failed in Jenkins: stanbol-trunk-1.6 #1484

See Changes: [rwesten] STANBOL-760: added sentiment-summarization engine to the engines bundlelist [rwesten] STANBOL-760: improved java doc and some code clean ups [enridaga] STANBOL-1164 Added the template to the expected location

Re: Commit window for 0.x release in trunk closes this Friday

Hi, thanks for the responses. I have no problem with delaying the closing of the release window a bit. But we have to do a cut in the next days and proceed. @Rafa: Do you have a date in mind when you will have finished your tasks? For the integration-tests issue, would be really great to have th

Re: Update on integration test problems

Hi Andreas, all Andreas was sending me several mails with log files for further tracing down his problem. With this mail I will try to summarize the current state. This mail discusses logs in the error.log file after running the integration-tests. This file can be found at integration-tests

Re: Commit window for 0.x release in trunk closes this Friday

Hi all, As I told Rupert yesterday, I have also a couple of issues almost finished, but unfortunately I'm not going to have time until next week to properly finish them, so I'm not in time for this release. Cheers, Rafa Haro El 18/10/13 12:03, Enrico Daga escribió: Hi Andreas, I have remove

Re: Commit window for 0.x release in trunk closes this Friday

Hi Andreas, I have removed all stanbol artifacts from my local repo, then run mvn clean install (on stanbol/trunk) Everything went smoothly. I have: java version "1.6.0_51" Java(TM) SE Runtime Environment (build 1.6.0_51-b11-456-11M4508) Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-456, mix

Re: Commit window for 0.x release in trunk closes this Friday

Rupert Westenthaler: > * Further looking into the build issues of Andreas: The Security > Exceptions of the FST linking engine are already solved. But the > Entityhub tests are still failing for some reason I do not understand > yet. I would like to know how representative my experience is regardi

Re: Commit window for 0.x release in trunk closes this Friday

HI Fabian, all I worked through all the open STANBOL issues and urge also other Stanbol committers to do the same. My TODOs are * Sentiment Summarization engine: No functional changes, but I would like to improving JavaDocs and also the documentation on the Webpage (that currently only links to