You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stanbol.apache.org by Fabian Christ <ch...@googlemail.com> on 2013/10/16 10:38:32 UTC

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

Hi,

we have been discussing this for a while but now it is time for action ;)

I would like to close the commit window for the last 0.x release this
Friday. Please, make sure that you have committed your pending changes
to the trunk.

I will create a release branch from the trunk and cut the release in
the upcoming days. In parallel the ng-branch will become the new trunk
for further development and the then obsolete ng-branch gets removed.

Any objections?

Best,
 - Fabian

-- 
Fabian
http://twitter.com/fctwitt

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

Posted by Rupert Westenthaler <ru...@gmail.com>.

Hi Fabian, all

On Wed, Oct 16, 2013 at 10:38 AM, Fabian Christ
<ch...@googlemail.com> wrote:
>
> Any objections?

Generally +1

I will have a look at all currently open Stanbol Issues and try to
schedule those relevant for the upcoming release to "0.12.0". After
that it should be more clear if the target Friday 18.Oct is feasible.

best
Rupert

-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

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

Posted by Fabian Christ <ch...@googlemail.com>.

Hi,

sure having binary releases of the launchers would be great.

My main concern of not doing this so far was, that it requires to
create the required LICENSE and NOTICE files for such a release. That
means that we have to check every single artifact that we include in
the binary release and add the required information to LICENSE and
NOTICE.

Since we were only doing source releases so far, there was no need for
this because in a source release the dependencies are not included and
only referenced. This is different in a binary release where we ship
everything in one package. So be prepared for this extra work.

Best,
 - Fabian

2013/10/21 Rupert Westenthaler <ru...@gmail.com>:
> Hi all,
>
> I was considering to create Stanbol launchers without data bundles in
> the release branch. This would allow us to do a binary release.
>
> We could create launchers for
>
> * stateless (Enhancer & Entityhub)
> * semindexing (Stateless & Contenthub & CMS Adapter)
> * reasoning (Ontologymanager & Rules & Reasoning)
> * full (all stanbol modules)
>
> In addition we could include the Entityhub indexing tools as binary releases.
>
> WDYT
> Rupert
>
> On Mon, Oct 21, 2013 at 1:12 PM, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:
>> Hi Fabian
>>
>> As we might need to build more release candidates I suggest to do this in
>> the release branch. For the release plugin to work it will afaik be
>> necessary to adapt the svn url in the pom
>>
>> Cheers,
>> Reto
>>
>>
>> On Sat, Oct 19, 2013 at 1:39 PM, Fabian Christ <christ.fabian@googlemail.com
>>> wrote:
>>
>>> Hi,
>>>
>>> good to hear about the progress ;)
>>>
>>> I am currently checking that the trunk is fine when trying to build
>>> with the apache-release profile (this includes the RAT check). Once
>>> this succeeds we could create the release branch.
>>>
>>> Best,
>>>  - Fabian
>>>
>>> 2013/10/19 Andreas Kuckartz <a....@ping.de>:
>>> > Rupert Westenthaler:
>>> >> However there is still no progress on the build issues of Andreas. As
>>> >> explained in [4] I can see in the log what is going wrong, but I have
>>> >> still no idea why this is happening in Andreas environment. All my
>>> >> tries to reproduce this where not successful.
>>> >
>>> > I have executed and am executing more experiments with the integration
>>> > tests and will report today or tomorrow. I think that I observed
>>> > something during the start of the launcher which might or might not have
>>> > something to do with the issues.
>>> >
>>> > A good thing is that I have no problem reproducing the issues ;-)
>>> >
>>> >> Still I would suggest to close the trunk for new things ASAP. Release
>>> >> related bug fixes can still be done during the release preparation and
>>> >> while checking/voting for the release candidates.
>>> >
>>> > +1
>>> >
>>> > Cheers,
>>> > Andreas
>>>
>>>
>>>
>>> --
>>> Fabian
>>> http://twitter.com/fctwitt
>>>
>
>
>
> --
> | Rupert Westenthaler             rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen



-- 
Fabian
http://twitter.com/fctwitt

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

Posted by Fabian Christ <ch...@googlemail.com>.

Hi Reto,

right - I have just updated the SCM information in the branch a
committed a few changes regarding missing headers and fixing POMs.

Best,
 - Fabian

2013/10/21 Reto Bachmann-Gmür <re...@wymiwyg.com>:
> Hi Fabian
>
> As we might need to build more release candidates I suggest to do this in
> the release branch. For the release plugin to work it will afaik be
> necessary to adapt the svn url in the pom
>
> Cheers,
> Reto
>
>
> On Sat, Oct 19, 2013 at 1:39 PM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> Hi,
>>
>> good to hear about the progress ;)
>>
>> I am currently checking that the trunk is fine when trying to build
>> with the apache-release profile (this includes the RAT check). Once
>> this succeeds we could create the release branch.
>>
>> Best,
>>  - Fabian
>>
>> 2013/10/19 Andreas Kuckartz <a....@ping.de>:
>> > Rupert Westenthaler:
>> >> However there is still no progress on the build issues of Andreas. As
>> >> explained in [4] I can see in the log what is going wrong, but I have
>> >> still no idea why this is happening in Andreas environment. All my
>> >> tries to reproduce this where not successful.
>> >
>> > I have executed and am executing more experiments with the integration
>> > tests and will report today or tomorrow. I think that I observed
>> > something during the start of the launcher which might or might not have
>> > something to do with the issues.
>> >
>> > A good thing is that I have no problem reproducing the issues ;-)
>> >
>> >> Still I would suggest to close the trunk for new things ASAP. Release
>> >> related bug fixes can still be done during the release preparation and
>> >> while checking/voting for the release candidates.
>> >
>> > +1
>> >
>> > Cheers,
>> > Andreas
>>
>>
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>



-- 
Fabian
http://twitter.com/fctwitt

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

Posted by Rupert Westenthaler <ru...@gmail.com>.

Hi all,

I was considering to create Stanbol launchers without data bundles in
the release branch. This would allow us to do a binary release.

We could create launchers for

* stateless (Enhancer & Entityhub)
* semindexing (Stateless & Contenthub & CMS Adapter)
* reasoning (Ontologymanager & Rules & Reasoning)
* full (all stanbol modules)

In addition we could include the Entityhub indexing tools as binary releases.

WDYT
Rupert

On Mon, Oct 21, 2013 at 1:12 PM, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:
> Hi Fabian
>
> As we might need to build more release candidates I suggest to do this in
> the release branch. For the release plugin to work it will afaik be
> necessary to adapt the svn url in the pom
>
> Cheers,
> Reto
>
>
> On Sat, Oct 19, 2013 at 1:39 PM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> Hi,
>>
>> good to hear about the progress ;)
>>
>> I am currently checking that the trunk is fine when trying to build
>> with the apache-release profile (this includes the RAT check). Once
>> this succeeds we could create the release branch.
>>
>> Best,
>>  - Fabian
>>
>> 2013/10/19 Andreas Kuckartz <a....@ping.de>:
>> > Rupert Westenthaler:
>> >> However there is still no progress on the build issues of Andreas. As
>> >> explained in [4] I can see in the log what is going wrong, but I have
>> >> still no idea why this is happening in Andreas environment. All my
>> >> tries to reproduce this where not successful.
>> >
>> > I have executed and am executing more experiments with the integration
>> > tests and will report today or tomorrow. I think that I observed
>> > something during the start of the launcher which might or might not have
>> > something to do with the issues.
>> >
>> > A good thing is that I have no problem reproducing the issues ;-)
>> >
>> >> Still I would suggest to close the trunk for new things ASAP. Release
>> >> related bug fixes can still be done during the release preparation and
>> >> while checking/voting for the release candidates.
>> >
>> > +1
>> >
>> > Cheers,
>> > Andreas
>>
>>
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

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

Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.

Hi Fabian

As we might need to build more release candidates I suggest to do this in
the release branch. For the release plugin to work it will afaik be
necessary to adapt the svn url in the pom

Cheers,
Reto


On Sat, Oct 19, 2013 at 1:39 PM, Fabian Christ <christ.fabian@googlemail.com
> wrote:

> Hi,
>
> good to hear about the progress ;)
>
> I am currently checking that the trunk is fine when trying to build
> with the apache-release profile (this includes the RAT check). Once
> this succeeds we could create the release branch.
>
> Best,
>  - Fabian
>
> 2013/10/19 Andreas Kuckartz <a....@ping.de>:
> > Rupert Westenthaler:
> >> However there is still no progress on the build issues of Andreas. As
> >> explained in [4] I can see in the log what is going wrong, but I have
> >> still no idea why this is happening in Andreas environment. All my
> >> tries to reproduce this where not successful.
> >
> > I have executed and am executing more experiments with the integration
> > tests and will report today or tomorrow. I think that I observed
> > something during the start of the launcher which might or might not have
> > something to do with the issues.
> >
> > A good thing is that I have no problem reproducing the issues ;-)
> >
> >> Still I would suggest to close the trunk for new things ASAP. Release
> >> related bug fixes can still be done during the release preparation and
> >> while checking/voting for the release candidates.
> >
> > +1
> >
> > Cheers,
> > Andreas
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>

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

Posted by Fabian Christ <ch...@googlemail.com>.

Hi,

good to hear about the progress ;)

I am currently checking that the trunk is fine when trying to build
with the apache-release profile (this includes the RAT check). Once
this succeeds we could create the release branch.

Best,
 - Fabian

2013/10/19 Andreas Kuckartz <a....@ping.de>:
> Rupert Westenthaler:
>> However there is still no progress on the build issues of Andreas. As
>> explained in [4] I can see in the log what is going wrong, but I have
>> still no idea why this is happening in Andreas environment. All my
>> tries to reproduce this where not successful.
>
> I have executed and am executing more experiments with the integration
> tests and will report today or tomorrow. I think that I observed
> something during the start of the launcher which might or might not have
> something to do with the issues.
>
> A good thing is that I have no problem reproducing the issues ;-)
>
>> Still I would suggest to close the trunk for new things ASAP. Release
>> related bug fixes can still be done during the release preparation and
>> while checking/voting for the release candidates.
>
> +1
>
> Cheers,
> Andreas



-- 
Fabian
http://twitter.com/fctwitt

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

Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.

Hi Andreas,




> Is more than "svn up" required for trunk ?
>

No, that's enough

>
> > Hope it won't break too many things...
>
> [INFO] Building Apache Stanbol Launchers Mini Launcher 1.0.0-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> Downloading:
>
> http://repository.apache.org/snapshots/org/apache/clerezza/provisioning/rdf/0.1-SNAPSHOT/maven-metadata.xml
> Downloading:
>
> http://repository.apache.org/snapshots/org/apache/clerezza/provisioning/rdf/0.1-SNAPSHOT/rdf-0.1-SNAPSHOT.pom
> [WARNING] The POM for
> org.apache.clerezza.provisioning:rdf:xml:0.1-SNAPSHOT is missing, no
> dependency information available
>

Sorry for this, it's fixed now.

Cheers,
Reto

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

Posted by Andreas Kuckartz <a....@ping.de>.

Reto Bachmann-Gmür:
> Ok I did the move.
> 
> Please switch your working copy appropriately or get a clean wokring
> environment with a fresh checkout.

Is more than "svn up" required for trunk ?

> Hope it won't break too many things...

[INFO] Building Apache Stanbol Launchers Mini Launcher 1.0.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
Downloading:
http://repository.apache.org/snapshots/org/apache/clerezza/provisioning/rdf/0.1-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/clerezza/provisioning/rdf/0.1-SNAPSHOT/rdf-0.1-SNAPSHOT.pom
[WARNING] The POM for
org.apache.clerezza.provisioning:rdf:xml:0.1-SNAPSHOT is missing, no
dependency information available

Cheers,
Andreas

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

Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.

Ok I did the move.

Please switch your working copy appropriately or get a clean wokring
environment with a fresh checkout.

Hope it won't break too many things...

Reto


On Mon, Oct 21, 2013 at 12:54 PM, Rafa Haro <rh...@zaizi.com> wrote:

> +1 also
>
> El 21/10/13 12:33, Rupert Westenthaler escribió:
>
>  ok with me
>>
>> On Mon, Oct 21, 2013 at 12:22 PM, Enrico Daga <en...@gmail.com>
>> wrote:
>>
>>> +1 for me
>>>
>>> Cheers,
>>> Enrico
>>>
>>>
>>> On 21 October 2013 11:16, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:
>>>
>>>  So it looks like the main problems and we no longer need to port a
>>>> moving
>>>> target to ng!
>>>>
>>>> so...
>>>>
>>>> svn mv https://svn.apache.org/repos/**asf/stanbol/trunk/<https://svn.apache.org/repos/asf/stanbol/trunk/>
>>>> https://svn.apache.org/repos/**asf/stanbol/branches/release-**0.12<https://svn.apache.org/repos/asf/stanbol/branches/release-0.12>
>>>> svn mv https://svn.apache.org/repos/**asf/stanbol/branches/commons-**
>>>> ng/ <https://svn.apache.org/repos/asf/stanbol/branches/commons-ng/>
>>>> https://svn.apache.org/repos/**asf/stanbol/trunk/<https://svn.apache.org/repos/asf/stanbol/trunk/>
>>>>
>>>> What happens after that move:
>>>> - in the releases branch development goes on tworatds the 0.12 release
>>>> - In trunk develoment goes towards 1.0.0 release. Most components are
>>>> there, some minor issues/test failures after recent merges with trunk
>>>> but
>>>> I'm sure that these can be fixed quickly.
>>>>
>>>> So to stop the duplication of work with the permanent porting I
>>>> suiggest we
>>>> do it now. ANy objection?
>>>>
>>>> Cheers,
>>>> Reto
>>>>
>>>>
>>>> On Sun, Oct 20, 2013 at 10:02 AM, Rupert Westenthaler <
>>>> rupert.westenthaler@gmail.com> wrote:
>>>>
>>>>  Hi Andreas,
>>>>>
>>>>> So it is confirmed that your problem is because - for some unknown
>>>>> reason - the integration-test on your platform does not wait until the
>>>>> dbpedia Site is ready.
>>>>>
>>>>>  I am waiting for the seconds because I noted that accessing the URL:
>>>>>>
>>>>>>
>>>>>>  http://localhost:5679/**entityhub/sites/referenced?**
>>>> header_Accept=application/json<http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json>
>>>>
>>>>> in a browser resulted in
>>>>>>     []
>>>>>>
>>>>>>  This is expected. The SiteManager starts and reports that no Site is
>>>>> yet present ... therefore the empty JSON Array
>>>>>
>>>>>  immediately after "[main] Startup completed" was output and only
>>>>>>
>>>>> changed
>>>>
>>>>> to
>>>>>
>>>>>>     ["http:\/\/localhost:5679\/**entityhub\/site\/dbpedia\/"]
>>>>>>
>>>>>> when I reloaded the URL again a few seconds later.
>>>>>>
>>>>> Since the update to a new dbpedia default data index the archive is
>>>>> bz2 compressed. Uncompressing this needs ~5sec. Because of that is
>>>>> does take some time before the dbpedia referenced site is available.
>>>>>
>>>>> The integration-test does send requests to
>>>>> 'entityhub/sites/referenced' and checks for
>>>>> "http:\/\/.*\/entityhub\/site\**/dbpedia\/" in the response (see [1]
>>>>> line 96). Only if this line is present a test is executed. This test
>>>>> is repeated for every single test.
>>>>>
>>>>> Yesterday I validated that this is working by manually starting a
>>>>> Stanbol launcher. After that I deactivated the DBpedia ReferencedSite
>>>>> and started the integration tests. As expected the tests kept waiting
>>>>> until I started the DBpedia ReferencedSite. After that the check went
>>>>> fine and the tests completed successfully.
>>>>>
>>>>> So my assumption is that this check does not work for you for some
>>>>>
>>>> reason.
>>>>
>>>>> best
>>>>> Rupert
>>>>>
>>>>>
>>>>>
>>>>> [1]
>>>>>
>>>>>  https://svn.apache.org/repos/**asf/stanbol/trunk/entityhub/**
>>>> generic/test/src/main/java/**org/apache/stanbol/entityhub/**
>>>> test/it/EntityhubTestBase.java<https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/generic/test/src/main/java/org/apache/stanbol/entityhub/test/it/EntityhubTestBase.java>
>>>>
>>>>>
>>>>> On Sat, Oct 19, 2013 at 9:02 PM, Andreas Kuckartz <a....@ping.de>
>>>>> wrote:
>>>>>
>>>>>> Andreas Kuckartz:
>>>>>>
>>>>>>> I have executed and am executing more experiments with the
>>>>>>> integration
>>>>>>> tests and will report today or tomorrow. I think that I observed
>>>>>>> something during the start of the launcher which might or might not
>>>>>>>
>>>>>> have
>>>>
>>>>> something to do with the issues.
>>>>>>>
>>>>>>> A good thing is that I have no problem reproducing the issues ;-)
>>>>>>>
>>>>>> And now am also able to successfully run the integration test :-)
>>>>>>
>>>>>> To do that I first start the launcher:
>>>>>>
>>>>>> $ cd integration-tests
>>>>>> $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679
>>>>>>
>>>>>> I then wait until I see "[main] Startup completed" and then wait for
>>>>>> an
>>>>>> additional ten seconds.
>>>>>>
>>>>>> Then I manually start the integration test in another console in the
>>>>>> same directory:
>>>>>>
>>>>>> $ mvn -o test -Dtest.server.url=http://**localhost:5679<http://localhost:5679>
>>>>>>
>>>>>> This ends with: BUILD SUCCESS
>>>>>>
>>>>>> If I start the test earlier it fails with many failures. So for some
>>>>>> reason the test does not correctly wait for the launcher.
>>>>>>
>>>>>> ***
>>>>>>
>>>>>> I am waiting for the seconds because I noted that accessing the URL:
>>>>>>
>>>>>>
>>>>>>  http://localhost:5679/**entityhub/sites/referenced?**
>>>> header_Accept=application/json<http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json>
>>>>
>>>>> in a browser resulted in
>>>>>>     []
>>>>>>
>>>>>> immediately after "[main] Startup completed" was output and only
>>>>>>
>>>>> changed
>>>>
>>>>> to
>>>>>
>>>>>>     ["http:\/\/localhost:5679\/**entityhub\/site\/dbpedia\/"]
>>>>>>
>>>>>> when I reloaded the URL again a few seconds later.
>>>>>>
>>>>>> Cheers,
>>>>>> Andreas
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> | Rupert Westenthaler             rupert.westenthaler@gmail.com
>>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>>> | A-5500 Bischofshofen
>>>>>
>>>>>
>>>
>>> --
>>> Enrico Daga
>>>
>>> --
>>> http://www.enridaga.net
>>> skype: enri-pan
>>>
>>
>>
>>
>
> --
>
> ------------------------------
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> London W6 7AN.
>

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

Posted by Rafa Haro <rh...@zaizi.com>.

+1 also

El 21/10/13 12:33, Rupert Westenthaler escribió:
> ok with me
>
> On Mon, Oct 21, 2013 at 12:22 PM, Enrico Daga <en...@gmail.com> wrote:
>> +1 for me
>>
>> Cheers,
>> Enrico
>>
>>
>> On 21 October 2013 11:16, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:
>>
>>> So it looks like the main problems and we no longer need to port a moving
>>> target to ng!
>>>
>>> so...
>>>
>>> svn mv https://svn.apache.org/repos/asf/stanbol/trunk/
>>> https://svn.apache.org/repos/asf/stanbol/branches/release-0.12
>>> svn mv https://svn.apache.org/repos/asf/stanbol/branches/commons-ng/
>>> https://svn.apache.org/repos/asf/stanbol/trunk/
>>>
>>> What happens after that move:
>>> - in the releases branch development goes on tworatds the 0.12 release
>>> - In trunk develoment goes towards 1.0.0 release. Most components are
>>> there, some minor issues/test failures after recent merges with trunk but
>>> I'm sure that these can be fixed quickly.
>>>
>>> So to stop the duplication of work with the permanent porting I suiggest we
>>> do it now. ANy objection?
>>>
>>> Cheers,
>>> Reto
>>>
>>>
>>> On Sun, Oct 20, 2013 at 10:02 AM, Rupert Westenthaler <
>>> rupert.westenthaler@gmail.com> wrote:
>>>
>>>> Hi Andreas,
>>>>
>>>> So it is confirmed that your problem is because - for some unknown
>>>> reason - the integration-test on your platform does not wait until the
>>>> dbpedia Site is ready.
>>>>
>>>>> I am waiting for the seconds because I noted that accessing the URL:
>>>>>
>>>>>
>>> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
>>>>> in a browser resulted in
>>>>>     []
>>>>>
>>>> This is expected. The SiteManager starts and reports that no Site is
>>>> yet present ... therefore the empty JSON Array
>>>>
>>>>> immediately after "[main] Startup completed" was output and only
>>> changed
>>>> to
>>>>>     ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
>>>>>
>>>>> when I reloaded the URL again a few seconds later.
>>>> Since the update to a new dbpedia default data index the archive is
>>>> bz2 compressed. Uncompressing this needs ~5sec. Because of that is
>>>> does take some time before the dbpedia referenced site is available.
>>>>
>>>> The integration-test does send requests to
>>>> 'entityhub/sites/referenced' and checks for
>>>> "http:\/\/.*\/entityhub\/site\/dbpedia\/" in the response (see [1]
>>>> line 96). Only if this line is present a test is executed. This test
>>>> is repeated for every single test.
>>>>
>>>> Yesterday I validated that this is working by manually starting a
>>>> Stanbol launcher. After that I deactivated the DBpedia ReferencedSite
>>>> and started the integration tests. As expected the tests kept waiting
>>>> until I started the DBpedia ReferencedSite. After that the check went
>>>> fine and the tests completed successfully.
>>>>
>>>> So my assumption is that this check does not work for you for some
>>> reason.
>>>> best
>>>> Rupert
>>>>
>>>>
>>>>
>>>> [1]
>>>>
>>> https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/generic/test/src/main/java/org/apache/stanbol/entityhub/test/it/EntityhubTestBase.java
>>>>
>>>> On Sat, Oct 19, 2013 at 9:02 PM, Andreas Kuckartz <a....@ping.de>
>>>> wrote:
>>>>> Andreas Kuckartz:
>>>>>> I have executed and am executing more experiments with the integration
>>>>>> tests and will report today or tomorrow. I think that I observed
>>>>>> something during the start of the launcher which might or might not
>>> have
>>>>>> something to do with the issues.
>>>>>>
>>>>>> A good thing is that I have no problem reproducing the issues ;-)
>>>>> And now am also able to successfully run the integration test :-)
>>>>>
>>>>> To do that I first start the launcher:
>>>>>
>>>>> $ cd integration-tests
>>>>> $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679
>>>>>
>>>>> I then wait until I see "[main] Startup completed" and then wait for an
>>>>> additional ten seconds.
>>>>>
>>>>> Then I manually start the integration test in another console in the
>>>>> same directory:
>>>>>
>>>>> $ mvn -o test -Dtest.server.url=http://localhost:5679
>>>>>
>>>>> This ends with: BUILD SUCCESS
>>>>>
>>>>> If I start the test earlier it fails with many failures. So for some
>>>>> reason the test does not correctly wait for the launcher.
>>>>>
>>>>> ***
>>>>>
>>>>> I am waiting for the seconds because I noted that accessing the URL:
>>>>>
>>>>>
>>> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
>>>>> in a browser resulted in
>>>>>     []
>>>>>
>>>>> immediately after "[main] Startup completed" was output and only
>>> changed
>>>> to
>>>>>     ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
>>>>>
>>>>> when I reloaded the URL again a few seconds later.
>>>>>
>>>>> Cheers,
>>>>> Andreas
>>>>
>>>>
>>>> --
>>>> | Rupert Westenthaler             rupert.westenthaler@gmail.com
>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>> | A-5500 Bischofshofen
>>>>
>>
>>
>> --
>> Enrico Daga
>>
>> --
>> http://www.enridaga.net
>> skype: enri-pan
>
>


-- 

------------------------------
This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately. 
Statements of intent shall only become binding when confirmed in hard copy 
by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 
6440931. The Registered Office is Brook House, 229 Shepherds Bush Road, 
London W6 7AN.

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

Posted by Rupert Westenthaler <ru...@gmail.com>.

ok with me

On Mon, Oct 21, 2013 at 12:22 PM, Enrico Daga <en...@gmail.com> wrote:
> +1 for me
>
> Cheers,
> Enrico
>
>
> On 21 October 2013 11:16, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:
>
>> So it looks like the main problems and we no longer need to port a moving
>> target to ng!
>>
>> so...
>>
>> svn mv https://svn.apache.org/repos/asf/stanbol/trunk/
>> https://svn.apache.org/repos/asf/stanbol/branches/release-0.12
>> svn mv https://svn.apache.org/repos/asf/stanbol/branches/commons-ng/
>> https://svn.apache.org/repos/asf/stanbol/trunk/
>>
>> What happens after that move:
>> - in the releases branch development goes on tworatds the 0.12 release
>> - In trunk develoment goes towards 1.0.0 release. Most components are
>> there, some minor issues/test failures after recent merges with trunk but
>> I'm sure that these can be fixed quickly.
>>
>> So to stop the duplication of work with the permanent porting I suiggest we
>> do it now. ANy objection?
>>
>> Cheers,
>> Reto
>>
>>
>> On Sun, Oct 20, 2013 at 10:02 AM, Rupert Westenthaler <
>> rupert.westenthaler@gmail.com> wrote:
>>
>> > Hi Andreas,
>> >
>> > So it is confirmed that your problem is because - for some unknown
>> > reason - the integration-test on your platform does not wait until the
>> > dbpedia Site is ready.
>> >
>> > > I am waiting for the seconds because I noted that accessing the URL:
>> > >
>> > >
>> >
>> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
>> > >
>> > > in a browser resulted in
>> > >    []
>> > >
>> >
>> > This is expected. The SiteManager starts and reports that no Site is
>> > yet present ... therefore the empty JSON Array
>> >
>> > > immediately after "[main] Startup completed" was output and only
>> changed
>> > to
>> > >    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
>> > >
>> > > when I reloaded the URL again a few seconds later.
>> >
>> > Since the update to a new dbpedia default data index the archive is
>> > bz2 compressed. Uncompressing this needs ~5sec. Because of that is
>> > does take some time before the dbpedia referenced site is available.
>> >
>> > The integration-test does send requests to
>> > 'entityhub/sites/referenced' and checks for
>> > "http:\/\/.*\/entityhub\/site\/dbpedia\/" in the response (see [1]
>> > line 96). Only if this line is present a test is executed. This test
>> > is repeated for every single test.
>> >
>> > Yesterday I validated that this is working by manually starting a
>> > Stanbol launcher. After that I deactivated the DBpedia ReferencedSite
>> > and started the integration tests. As expected the tests kept waiting
>> > until I started the DBpedia ReferencedSite. After that the check went
>> > fine and the tests completed successfully.
>> >
>> > So my assumption is that this check does not work for you for some
>> reason.
>> >
>> > best
>> > Rupert
>> >
>> >
>> >
>> > [1]
>> >
>> https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/generic/test/src/main/java/org/apache/stanbol/entityhub/test/it/EntityhubTestBase.java
>> >
>> >
>> > On Sat, Oct 19, 2013 at 9:02 PM, Andreas Kuckartz <a....@ping.de>
>> > wrote:
>> > > Andreas Kuckartz:
>> > >> I have executed and am executing more experiments with the integration
>> > >> tests and will report today or tomorrow. I think that I observed
>> > >> something during the start of the launcher which might or might not
>> have
>> > >> something to do with the issues.
>> > >>
>> > >> A good thing is that I have no problem reproducing the issues ;-)
>> > >
>> > > And now am also able to successfully run the integration test :-)
>> > >
>> > > To do that I first start the launcher:
>> > >
>> > > $ cd integration-tests
>> > > $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679
>> > >
>> > > I then wait until I see "[main] Startup completed" and then wait for an
>> > > additional ten seconds.
>> > >
>> > > Then I manually start the integration test in another console in the
>> > > same directory:
>> > >
>> > > $ mvn -o test -Dtest.server.url=http://localhost:5679
>> > >
>> > > This ends with: BUILD SUCCESS
>> > >
>> > > If I start the test earlier it fails with many failures. So for some
>> > > reason the test does not correctly wait for the launcher.
>> > >
>> > > ***
>> > >
>> > > I am waiting for the seconds because I noted that accessing the URL:
>> > >
>> > >
>> >
>> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
>> > >
>> > > in a browser resulted in
>> > >    []
>> > >
>> > > immediately after "[main] Startup completed" was output and only
>> changed
>> > to
>> > >    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
>> > >
>> > > when I reloaded the URL again a few seconds later.
>> > >
>> > > Cheers,
>> > > Andreas
>> >
>> >
>> >
>> > --
>> > | Rupert Westenthaler             rupert.westenthaler@gmail.com
>> > | Bodenlehenstraße 11                             ++43-699-11108907
>> > | A-5500 Bischofshofen
>> >
>>
>
>
>
> --
> Enrico Daga
>
> --
> http://www.enridaga.net
> skype: enri-pan



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

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

Posted by Enrico Daga <en...@gmail.com>.

+1 for me

Cheers,
Enrico


On 21 October 2013 11:16, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:

> So it looks like the main problems and we no longer need to port a moving
> target to ng!
>
> so...
>
> svn mv https://svn.apache.org/repos/asf/stanbol/trunk/
> https://svn.apache.org/repos/asf/stanbol/branches/release-0.12
> svn mv https://svn.apache.org/repos/asf/stanbol/branches/commons-ng/
> https://svn.apache.org/repos/asf/stanbol/trunk/
>
> What happens after that move:
> - in the releases branch development goes on tworatds the 0.12 release
> - In trunk develoment goes towards 1.0.0 release. Most components are
> there, some minor issues/test failures after recent merges with trunk but
> I'm sure that these can be fixed quickly.
>
> So to stop the duplication of work with the permanent porting I suiggest we
> do it now. ANy objection?
>
> Cheers,
> Reto
>
>
> On Sun, Oct 20, 2013 at 10:02 AM, Rupert Westenthaler <
> rupert.westenthaler@gmail.com> wrote:
>
> > Hi Andreas,
> >
> > So it is confirmed that your problem is because - for some unknown
> > reason - the integration-test on your platform does not wait until the
> > dbpedia Site is ready.
> >
> > > I am waiting for the seconds because I noted that accessing the URL:
> > >
> > >
> >
> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
> > >
> > > in a browser resulted in
> > >    []
> > >
> >
> > This is expected. The SiteManager starts and reports that no Site is
> > yet present ... therefore the empty JSON Array
> >
> > > immediately after "[main] Startup completed" was output and only
> changed
> > to
> > >    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
> > >
> > > when I reloaded the URL again a few seconds later.
> >
> > Since the update to a new dbpedia default data index the archive is
> > bz2 compressed. Uncompressing this needs ~5sec. Because of that is
> > does take some time before the dbpedia referenced site is available.
> >
> > The integration-test does send requests to
> > 'entityhub/sites/referenced' and checks for
> > "http:\/\/.*\/entityhub\/site\/dbpedia\/" in the response (see [1]
> > line 96). Only if this line is present a test is executed. This test
> > is repeated for every single test.
> >
> > Yesterday I validated that this is working by manually starting a
> > Stanbol launcher. After that I deactivated the DBpedia ReferencedSite
> > and started the integration tests. As expected the tests kept waiting
> > until I started the DBpedia ReferencedSite. After that the check went
> > fine and the tests completed successfully.
> >
> > So my assumption is that this check does not work for you for some
> reason.
> >
> > best
> > Rupert
> >
> >
> >
> > [1]
> >
> https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/generic/test/src/main/java/org/apache/stanbol/entityhub/test/it/EntityhubTestBase.java
> >
> >
> > On Sat, Oct 19, 2013 at 9:02 PM, Andreas Kuckartz <a....@ping.de>
> > wrote:
> > > Andreas Kuckartz:
> > >> I have executed and am executing more experiments with the integration
> > >> tests and will report today or tomorrow. I think that I observed
> > >> something during the start of the launcher which might or might not
> have
> > >> something to do with the issues.
> > >>
> > >> A good thing is that I have no problem reproducing the issues ;-)
> > >
> > > And now am also able to successfully run the integration test :-)
> > >
> > > To do that I first start the launcher:
> > >
> > > $ cd integration-tests
> > > $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679
> > >
> > > I then wait until I see "[main] Startup completed" and then wait for an
> > > additional ten seconds.
> > >
> > > Then I manually start the integration test in another console in the
> > > same directory:
> > >
> > > $ mvn -o test -Dtest.server.url=http://localhost:5679
> > >
> > > This ends with: BUILD SUCCESS
> > >
> > > If I start the test earlier it fails with many failures. So for some
> > > reason the test does not correctly wait for the launcher.
> > >
> > > ***
> > >
> > > I am waiting for the seconds because I noted that accessing the URL:
> > >
> > >
> >
> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
> > >
> > > in a browser resulted in
> > >    []
> > >
> > > immediately after "[main] Startup completed" was output and only
> changed
> > to
> > >    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
> > >
> > > when I reloaded the URL again a few seconds later.
> > >
> > > Cheers,
> > > Andreas
> >
> >
> >
> > --
> > | Rupert Westenthaler             rupert.westenthaler@gmail.com
> > | Bodenlehenstraße 11                             ++43-699-11108907
> > | A-5500 Bischofshofen
> >
>



-- 
Enrico Daga

--
http://www.enridaga.net
skype: enri-pan

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

Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.

So it looks like the main problems and we no longer need to port a moving
target to ng!

so...

svn mv https://svn.apache.org/repos/asf/stanbol/trunk/
https://svn.apache.org/repos/asf/stanbol/branches/release-0.12
svn mv https://svn.apache.org/repos/asf/stanbol/branches/commons-ng/
https://svn.apache.org/repos/asf/stanbol/trunk/

What happens after that move:
- in the releases branch development goes on tworatds the 0.12 release
- In trunk develoment goes towards 1.0.0 release. Most components are
there, some minor issues/test failures after recent merges with trunk but
I'm sure that these can be fixed quickly.

So to stop the duplication of work with the permanent porting I suiggest we
do it now. ANy objection?

Cheers,
Reto


On Sun, Oct 20, 2013 at 10:02 AM, Rupert Westenthaler <
rupert.westenthaler@gmail.com> wrote:

> Hi Andreas,
>
> So it is confirmed that your problem is because - for some unknown
> reason - the integration-test on your platform does not wait until the
> dbpedia Site is ready.
>
> > I am waiting for the seconds because I noted that accessing the URL:
> >
> >
> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
> >
> > in a browser resulted in
> >    []
> >
>
> This is expected. The SiteManager starts and reports that no Site is
> yet present ... therefore the empty JSON Array
>
> > immediately after "[main] Startup completed" was output and only changed
> to
> >    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
> >
> > when I reloaded the URL again a few seconds later.
>
> Since the update to a new dbpedia default data index the archive is
> bz2 compressed. Uncompressing this needs ~5sec. Because of that is
> does take some time before the dbpedia referenced site is available.
>
> The integration-test does send requests to
> 'entityhub/sites/referenced' and checks for
> "http:\/\/.*\/entityhub\/site\/dbpedia\/" in the response (see [1]
> line 96). Only if this line is present a test is executed. This test
> is repeated for every single test.
>
> Yesterday I validated that this is working by manually starting a
> Stanbol launcher. After that I deactivated the DBpedia ReferencedSite
> and started the integration tests. As expected the tests kept waiting
> until I started the DBpedia ReferencedSite. After that the check went
> fine and the tests completed successfully.
>
> So my assumption is that this check does not work for you for some reason.
>
> best
> Rupert
>
>
>
> [1]
> https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/generic/test/src/main/java/org/apache/stanbol/entityhub/test/it/EntityhubTestBase.java
>
>
> On Sat, Oct 19, 2013 at 9:02 PM, Andreas Kuckartz <a....@ping.de>
> wrote:
> > Andreas Kuckartz:
> >> I have executed and am executing more experiments with the integration
> >> tests and will report today or tomorrow. I think that I observed
> >> something during the start of the launcher which might or might not have
> >> something to do with the issues.
> >>
> >> A good thing is that I have no problem reproducing the issues ;-)
> >
> > And now am also able to successfully run the integration test :-)
> >
> > To do that I first start the launcher:
> >
> > $ cd integration-tests
> > $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679
> >
> > I then wait until I see "[main] Startup completed" and then wait for an
> > additional ten seconds.
> >
> > Then I manually start the integration test in another console in the
> > same directory:
> >
> > $ mvn -o test -Dtest.server.url=http://localhost:5679
> >
> > This ends with: BUILD SUCCESS
> >
> > If I start the test earlier it fails with many failures. So for some
> > reason the test does not correctly wait for the launcher.
> >
> > ***
> >
> > I am waiting for the seconds because I noted that accessing the URL:
> >
> >
> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
> >
> > in a browser resulted in
> >    []
> >
> > immediately after "[main] Startup completed" was output and only changed
> to
> >    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
> >
> > when I reloaded the URL again a few seconds later.
> >
> > Cheers,
> > Andreas
>
>
>
> --
> | Rupert Westenthaler             rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen
>

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

Posted by Rupert Westenthaler <ru...@gmail.com>.

Hi Andreas,

So it is confirmed that your problem is because - for some unknown
reason - the integration-test on your platform does not wait until the
dbpedia Site is ready.

> I am waiting for the seconds because I noted that accessing the URL:
>
> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
>
> in a browser resulted in
>    []
>

This is expected. The SiteManager starts and reports that no Site is
yet present ... therefore the empty JSON Array

> immediately after "[main] Startup completed" was output and only changed to
>    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
>
> when I reloaded the URL again a few seconds later.

Since the update to a new dbpedia default data index the archive is
bz2 compressed. Uncompressing this needs ~5sec. Because of that is
does take some time before the dbpedia referenced site is available.

The integration-test does send requests to
'entityhub/sites/referenced' and checks for
"http:\/\/.*\/entityhub\/site\/dbpedia\/" in the response (see [1]
line 96). Only if this line is present a test is executed. This test
is repeated for every single test.

Yesterday I validated that this is working by manually starting a
Stanbol launcher. After that I deactivated the DBpedia ReferencedSite
and started the integration tests. As expected the tests kept waiting
until I started the DBpedia ReferencedSite. After that the check went
fine and the tests completed successfully.

So my assumption is that this check does not work for you for some reason.

best
Rupert

[1] https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/generic/test/src/main/java/org/apache/stanbol/entityhub/test/it/EntityhubTestBase.java

On Sat, Oct 19, 2013 at 9:02 PM, Andreas Kuckartz <a....@ping.de> wrote:
> Andreas Kuckartz:
>> I have executed and am executing more experiments with the integration
>> tests and will report today or tomorrow. I think that I observed
>> something during the start of the launcher which might or might not have
>> something to do with the issues.
>>
>> A good thing is that I have no problem reproducing the issues ;-)
>
> And now am also able to successfully run the integration test :-)
>
> To do that I first start the launcher:
>
> $ cd integration-tests
> $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679
>
> I then wait until I see "[main] Startup completed" and then wait for an
> additional ten seconds.
>
> Then I manually start the integration test in another console in the
> same directory:
>
> $ mvn -o test -Dtest.server.url=http://localhost:5679
>
> This ends with: BUILD SUCCESS
>
> If I start the test earlier it fails with many failures. So for some
> reason the test does not correctly wait for the launcher.
>
> ***
>
> I am waiting for the seconds because I noted that accessing the URL:
>
> http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json
>
> in a browser resulted in
>    []
>
> immediately after "[main] Startup completed" was output and only changed to
>    ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]
>
> when I reloaded the URL again a few seconds later.
>
> Cheers,
> Andreas

-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

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

Posted by Andreas Kuckartz <a....@ping.de>.

Andreas Kuckartz:
> I have executed and am executing more experiments with the integration
> tests and will report today or tomorrow. I think that I observed
> something during the start of the launcher which might or might not have
> something to do with the issues.
> 
> A good thing is that I have no problem reproducing the issues ;-)

And now am also able to successfully run the integration test :-)

To do that I first start the launcher:

$ cd integration-tests
$ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679

I then wait until I see "[main] Startup completed" and then wait for an
additional ten seconds.

Then I manually start the integration test in another console in the
same directory:

$ mvn -o test -Dtest.server.url=http://localhost:5679

This ends with: BUILD SUCCESS

If I start the test earlier it fails with many failures. So for some
reason the test does not correctly wait for the launcher.

***

I am waiting for the seconds because I noted that accessing the URL:

http://localhost:5679/entityhub/sites/referenced?header_Accept=application/json

in a browser resulted in
   []

immediately after "[main] Startup completed" was output and only changed to
   ["http:\/\/localhost:5679\/entityhub\/site\/dbpedia\/"]

when I reloaded the URL again a few seconds later.

Cheers,
Andreas

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

Posted by Andreas Kuckartz <a....@ping.de>.

Rupert Westenthaler:
> However there is still no progress on the build issues of Andreas. As
> explained in [4] I can see in the log what is going wrong, but I have
> still no idea why this is happening in Andreas environment. All my
> tries to reproduce this where not successful.

I have executed and am executing more experiments with the integration
tests and will report today or tomorrow. I think that I observed
something during the start of the launcher which might or might not have
something to do with the issues.

A good thing is that I have no problem reproducing the issues ;-)

> Still I would suggest to close the trunk for new things ASAP. Release
> related bug fixes can still be done during the release preparation and
> while checking/voting for the release candidates.

+1

Cheers,
Andreas

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

Posted by Rupert Westenthaler <ru...@gmail.com>.

Hi all,

I fixed the issue mentioned by Reto [1]. Also reverted an
unintentional upgrade to Tika 1.4 [2] in the enhancer bundlelist with
[3].

However there is still no progress on the build issues of Andreas. As
explained in [4] I can see in the log what is going wrong, but I have
still no idea why this is happening in Andreas environment. All my
tries to reproduce this where not successful.

Still I would suggest to close the trunk for new things ASAP. Release
related bug fixes can still be done during the release preparation and
while checking/voting for the release candidates.

WDYT
Rupert

[1] http://mail-archives.apache.org/mod_mbox/stanbol-dev/201310.mbox/%3CCALvhUEW8mf0URO8zPBmOzVmti%2Bjqusxa6h7KFK7KwkbNWXW7nQ%40mail.gmail.com%3E
[2] http://svn.apache.org/r1533422
[3] http://svn.apache.org/r1533715
[4] http://markmail.org/message/qkliytcoev7ehidj

On Fri, Oct 18, 2013 at 8:22 PM, Rafa Haro <rh...@zaizi.com> wrote:
> 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 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 development in trunk
>> goes towards 1.0.0.
>>
>> Cheers,
>> Reto
>>
>>
>> 1.
>>
>> http://mail-archives.apache.org/mod_mbox/stanbol-dev/201310.mbox/%3CCALvhUEW8mf0URO8zPBmOzVmti%2Bjqusxa6h7KFK7KwkbNWXW7nQ%40mail.gmail.com%3E
>>
>>
>>
>>
>> On Fri, Oct 18, 2013 at 7:32 PM, Rafa Haro <rharo@zaizi.com <javascript:;>>
>> wrote:
>>
>> > 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
>> > already wrote an email about it.
>> >
>> > Regards
>> >
>> > El viernes, 18 de octubre de 2013, Reto Bachmann-Gmür escribió:
>> >
>> > > 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.
>> > >
>> > > @Rafa: On the list I can't find the conversation betwwen you and
>> Rupert.
>> > > What are the issues you're working on?
>> > >
>> > > In general I would appreciate more discussions on the list about what's
>> > > going on. I see a huge lot of commits for which I can't find any list
>> > > discussion.
>> > >
>> > > Cheers,
>> > > Reto
>> > >
>> > >
>> > > On Fri, Oct 18, 2013 at 12:58 PM, Fabian Christ <
>> > > christ.fabian@googlemail.com <javascript:;> <javascript:;>> wrote:
>> > >
>> > > > 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 this
>> > > > solved. I am currently in the process of doing a clean build an a new
>> > > > machine.
>> > > >
>> > > > Best,
>> > > >  - Fabian
>> > > >
>> > > > 2013/10/18 Rafa Haro <rharo@zaizi.com <javascript:;><javascript:;>>:
>> > > > > 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 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, mixed
>> mode)
>> > > > >>
>> > > > >> (maybe problems are with Java 7)
>> > > > >>
>> > > > >> Anyway, I think if there is an unclosed problem with that and
>> > Andreas
>> > > > >> proposes to wait until it is fixed, we may also decide to move the
>> > > > >> development to the branch (much important thing IMHO), keep trunk
>> as
>> > > it
>> > > > is
>> > > > >> (freezed) but still waiting for the problem to be solved before
>> the
>> > > next
>> > > > >> release.
>> > > > >>
>> > > > >> WDYT?
>> > > > >>
>> > > > >>
>> > > > >> Cheers,
>> > > > >> Enrico
>> > > > >>
>> > > > >>
>> > > > >> On 18 October 2013 10:03, Andreas Kuckartz <a.kuckartz@ping.de<javascript:;>
>> > <javascript:;>>
>> > > wrote:
>> > > > >>
>> > > > >>> 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
>> regarding
>> > > > those
>> > > > >>> build/integration test errors.
>> > > > >>>
>> > > > >>> Question to all (with the exception of Rupert):
>> > > > >>>
>> > > > >>> Are you able to run "mvn clean install" without seeing a build
>> > error?
>> > > > >>> (And which environment are you using?)
>> > > > >>>
>> > > > >>> Cheers,
>> > > > >>> Andreas
>> > > > >>>
>> > > > >>
>> > > > >>
>> > > > >
>> > > > >
>> > > > > --
>> > > > >
>> > > > > ------------------------------
>> > > > > This message should be regarded as confidential. If you have
>> received
>> > > > this
>> > > > > email in error please notify the sender and destroy it immediately.
>> > > > > Statements of intent shall only become binding when confirmed in
>> hard
>> > > > copy
>> > > > > by an authorised signatory.
>> > > > >
>> > > > > Zaizi Ltd is registered in England and Wales with the registration
>> > > number
>> > > > > 6440931. The Registered Office is Brook House, 229 Shepherds Bush
>> > Road,
>> > > > > London W6 7AN.
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Fabian
>> > > > http://twitter.com/fctwitt
>> > > >
>> > >
>> >
>> > --
>> >
>> > ------------------------------
>> > This message should be regarded as confidential. If you have received
>> this
>> > email in error please notify the sender and destroy it immediately.
>> > Statements of intent shall only become binding when confirmed in hard
>> copy
>> > by an authorised signatory.
>> >
>> > Zaizi Ltd is registered in England and Wales with the registration number
>> > 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
>> > London W6 7AN.
>> >
>>
>
> --
>
> ------------------------------
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> London W6 7AN.



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

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

Posted by Rafa Haro <rh...@zaizi.com>.

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 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 development in trunk
> goes towards 1.0.0.
>
> Cheers,
> Reto
>
>
> 1.
>
> http://mail-archives.apache.org/mod_mbox/stanbol-dev/201310.mbox/%3CCALvhUEW8mf0URO8zPBmOzVmti%2Bjqusxa6h7KFK7KwkbNWXW7nQ%40mail.gmail.com%3E
>
>
>
>
> On Fri, Oct 18, 2013 at 7:32 PM, Rafa Haro <rharo@zaizi.com <javascript:;>>
> wrote:
>
> > 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
> > already wrote an email about it.
> >
> > Regards
> >
> > El viernes, 18 de octubre de 2013, Reto Bachmann-Gmür escribió:
> >
> > > 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.
> > >
> > > @Rafa: On the list I can't find the conversation betwwen you and
> Rupert.
> > > What are the issues you're working on?
> > >
> > > In general I would appreciate more discussions on the list about what's
> > > going on. I see a huge lot of commits for which I can't find any list
> > > discussion.
> > >
> > > Cheers,
> > > Reto
> > >
> > >
> > > On Fri, Oct 18, 2013 at 12:58 PM, Fabian Christ <
> > > christ.fabian@googlemail.com <javascript:;> <javascript:;>> wrote:
> > >
> > > > 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 this
> > > > solved. I am currently in the process of doing a clean build an a new
> > > > machine.
> > > >
> > > > Best,
> > > >  - Fabian
> > > >
> > > > 2013/10/18 Rafa Haro <rharo@zaizi.com <javascript:;><javascript:;>>:
> > > > > 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 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, mixed
> mode)
> > > > >>
> > > > >> (maybe problems are with Java 7)
> > > > >>
> > > > >> Anyway, I think if there is an unclosed problem with that and
> > Andreas
> > > > >> proposes to wait until it is fixed, we may also decide to move the
> > > > >> development to the branch (much important thing IMHO), keep trunk
> as
> > > it
> > > > is
> > > > >> (freezed) but still waiting for the problem to be solved before
> the
> > > next
> > > > >> release.
> > > > >>
> > > > >> WDYT?
> > > > >>
> > > > >>
> > > > >> Cheers,
> > > > >> Enrico
> > > > >>
> > > > >>
> > > > >> On 18 October 2013 10:03, Andreas Kuckartz <a.kuckartz@ping.de<javascript:;>
> > <javascript:;>>
> > > wrote:
> > > > >>
> > > > >>> 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
> regarding
> > > > those
> > > > >>> build/integration test errors.
> > > > >>>
> > > > >>> Question to all (with the exception of Rupert):
> > > > >>>
> > > > >>> Are you able to run "mvn clean install" without seeing a build
> > error?
> > > > >>> (And which environment are you using?)
> > > > >>>
> > > > >>> Cheers,
> > > > >>> Andreas
> > > > >>>
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > ------------------------------
> > > > > This message should be regarded as confidential. If you have
> received
> > > > this
> > > > > email in error please notify the sender and destroy it immediately.
> > > > > Statements of intent shall only become binding when confirmed in
> hard
> > > > copy
> > > > > by an authorised signatory.
> > > > >
> > > > > Zaizi Ltd is registered in England and Wales with the registration
> > > number
> > > > > 6440931. The Registered Office is Brook House, 229 Shepherds Bush
> > Road,
> > > > > London W6 7AN.
> > > >
> > > >
> > > >
> > > > --
> > > > Fabian
> > > > http://twitter.com/fctwitt
> > > >
> > >
> >
> > --
> >
> > ------------------------------
> > This message should be regarded as confidential. If you have received
> this
> > email in error please notify the sender and destroy it immediately.
> > Statements of intent shall only become binding when confirmed in hard
> copy
> > by an authorised signatory.
> >
> > Zaizi Ltd is registered in England and Wales with the registration number
> > 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> > London W6 7AN.
> >
>

-- 

------------------------------
This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately. 
Statements of intent shall only become binding when confirmed in hard copy 
by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 
6440931. The Registered Office is Brook House, 229 Shepherds Bush Road, 
London W6 7AN.

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

Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.

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 development in trunk
goes towards 1.0.0.

Cheers,
Reto


1.
http://mail-archives.apache.org/mod_mbox/stanbol-dev/201310.mbox/%3CCALvhUEW8mf0URO8zPBmOzVmti%2Bjqusxa6h7KFK7KwkbNWXW7nQ%40mail.gmail.com%3E




On Fri, Oct 18, 2013 at 7:32 PM, Rafa Haro <rh...@zaizi.com> wrote:

> 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
> already wrote an email about it.
>
> Regards
>
> El viernes, 18 de octubre de 2013, Reto Bachmann-Gmür escribió:
>
> > 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.
> >
> > @Rafa: On the list I can't find the conversation betwwen you and Rupert.
> > What are the issues you're working on?
> >
> > In general I would appreciate more discussions on the list about what's
> > going on. I see a huge lot of commits for which I can't find any list
> > discussion.
> >
> > Cheers,
> > Reto
> >
> >
> > On Fri, Oct 18, 2013 at 12:58 PM, Fabian Christ <
> > christ.fabian@googlemail.com <javascript:;>> wrote:
> >
> > > 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 this
> > > solved. I am currently in the process of doing a clean build an a new
> > > machine.
> > >
> > > Best,
> > >  - Fabian
> > >
> > > 2013/10/18 Rafa Haro <rharo@zaizi.com <javascript:;>>:
> > > > 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 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, mixed mode)
> > > >>
> > > >> (maybe problems are with Java 7)
> > > >>
> > > >> Anyway, I think if there is an unclosed problem with that and
> Andreas
> > > >> proposes to wait until it is fixed, we may also decide to move the
> > > >> development to the branch (much important thing IMHO), keep trunk as
> > it
> > > is
> > > >> (freezed) but still waiting for the problem to be solved before the
> > next
> > > >> release.
> > > >>
> > > >> WDYT?
> > > >>
> > > >>
> > > >> Cheers,
> > > >> Enrico
> > > >>
> > > >>
> > > >> On 18 October 2013 10:03, Andreas Kuckartz <a.kuckartz@ping.de
> <javascript:;>>
> > wrote:
> > > >>
> > > >>> 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 regarding
> > > those
> > > >>> build/integration test errors.
> > > >>>
> > > >>> Question to all (with the exception of Rupert):
> > > >>>
> > > >>> Are you able to run "mvn clean install" without seeing a build
> error?
> > > >>> (And which environment are you using?)
> > > >>>
> > > >>> Cheers,
> > > >>> Andreas
> > > >>>
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > ------------------------------
> > > > This message should be regarded as confidential. If you have received
> > > this
> > > > email in error please notify the sender and destroy it immediately.
> > > > Statements of intent shall only become binding when confirmed in hard
> > > copy
> > > > by an authorised signatory.
> > > >
> > > > Zaizi Ltd is registered in England and Wales with the registration
> > number
> > > > 6440931. The Registered Office is Brook House, 229 Shepherds Bush
> Road,
> > > > London W6 7AN.
> > >
> > >
> > >
> > > --
> > > Fabian
> > > http://twitter.com/fctwitt
> > >
> >
>
> --
>
> ------------------------------
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> London W6 7AN.
>

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

Posted by Rafa Haro <rh...@zaizi.com>.

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
already wrote an email about it.

Regards

El viernes, 18 de octubre de 2013, Reto Bachmann-Gmür escribió:

> 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.
>
> @Rafa: On the list I can't find the conversation betwwen you and Rupert.
> What are the issues you're working on?
>
> In general I would appreciate more discussions on the list about what's
> going on. I see a huge lot of commits for which I can't find any list
> discussion.
>
> Cheers,
> Reto
>
>
> On Fri, Oct 18, 2013 at 12:58 PM, Fabian Christ <
> christ.fabian@googlemail.com <javascript:;>> wrote:
>
> > 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 this
> > solved. I am currently in the process of doing a clean build an a new
> > machine.
> >
> > Best,
> >  - Fabian
> >
> > 2013/10/18 Rafa Haro <rharo@zaizi.com <javascript:;>>:
> > > 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 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, mixed mode)
> > >>
> > >> (maybe problems are with Java 7)
> > >>
> > >> Anyway, I think if there is an unclosed problem with that and Andreas
> > >> proposes to wait until it is fixed, we may also decide to move the
> > >> development to the branch (much important thing IMHO), keep trunk as
> it
> > is
> > >> (freezed) but still waiting for the problem to be solved before the
> next
> > >> release.
> > >>
> > >> WDYT?
> > >>
> > >>
> > >> Cheers,
> > >> Enrico
> > >>
> > >>
> > >> On 18 October 2013 10:03, Andreas Kuckartz <a.kuckartz@ping.de<javascript:;>>
> wrote:
> > >>
> > >>> 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 regarding
> > those
> > >>> build/integration test errors.
> > >>>
> > >>> Question to all (with the exception of Rupert):
> > >>>
> > >>> Are you able to run "mvn clean install" without seeing a build error?
> > >>> (And which environment are you using?)
> > >>>
> > >>> Cheers,
> > >>> Andreas
> > >>>
> > >>
> > >>
> > >
> > >
> > > --
> > >
> > > ------------------------------
> > > This message should be regarded as confidential. If you have received
> > this
> > > email in error please notify the sender and destroy it immediately.
> > > Statements of intent shall only become binding when confirmed in hard
> > copy
> > > by an authorised signatory.
> > >
> > > Zaizi Ltd is registered in England and Wales with the registration
> number
> > > 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> > > London W6 7AN.
> >
> >
> >
> > --
> > Fabian
> > http://twitter.com/fctwitt
> >
>

-- 

------------------------------
This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately. 
Statements of intent shall only become binding when confirmed in hard copy 
by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 
6440931. The Registered Office is Brook House, 229 Shepherds Bush Road, 
London W6 7AN.

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

Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.

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.

@Rafa: On the list I can't find the conversation betwwen you and Rupert.
What are the issues you're working on?

In general I would appreciate more discussions on the list about what's
going on. I see a huge lot of commits for which I can't find any list
discussion.

Cheers,
Reto


On Fri, Oct 18, 2013 at 12:58 PM, Fabian Christ <
christ.fabian@googlemail.com> wrote:

> 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 this
> solved. I am currently in the process of doing a clean build an a new
> machine.
>
> Best,
>  - Fabian
>
> 2013/10/18 Rafa Haro <rh...@zaizi.com>:
> > 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 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, mixed mode)
> >>
> >> (maybe problems are with Java 7)
> >>
> >> Anyway, I think if there is an unclosed problem with that and Andreas
> >> proposes to wait until it is fixed, we may also decide to move the
> >> development to the branch (much important thing IMHO), keep trunk as it
> is
> >> (freezed) but still waiting for the problem to be solved before the next
> >> release.
> >>
> >> WDYT?
> >>
> >>
> >> Cheers,
> >> Enrico
> >>
> >>
> >> On 18 October 2013 10:03, Andreas Kuckartz <a....@ping.de> wrote:
> >>
> >>> 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 regarding
> those
> >>> build/integration test errors.
> >>>
> >>> Question to all (with the exception of Rupert):
> >>>
> >>> Are you able to run "mvn clean install" without seeing a build error?
> >>> (And which environment are you using?)
> >>>
> >>> Cheers,
> >>> Andreas
> >>>
> >>
> >>
> >
> >
> > --
> >
> > ------------------------------
> > This message should be regarded as confidential. If you have received
> this
> > email in error please notify the sender and destroy it immediately.
> > Statements of intent shall only become binding when confirmed in hard
> copy
> > by an authorised signatory.
> >
> > Zaizi Ltd is registered in England and Wales with the registration number
> > 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> > London W6 7AN.
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>

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

Posted by Fabian Christ <ch...@googlemail.com>.

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 this
solved. I am currently in the process of doing a clean build an a new
machine.

Best,
 - Fabian

2013/10/18 Rafa Haro <rh...@zaizi.com>:
> 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 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, mixed mode)
>>
>> (maybe problems are with Java 7)
>>
>> Anyway, I think if there is an unclosed problem with that and Andreas
>> proposes to wait until it is fixed, we may also decide to move the
>> development to the branch (much important thing IMHO), keep trunk as it is
>> (freezed) but still waiting for the problem to be solved before the next
>> release.
>>
>> WDYT?
>>
>>
>> Cheers,
>> Enrico
>>
>>
>> On 18 October 2013 10:03, Andreas Kuckartz <a....@ping.de> wrote:
>>
>>> 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 regarding those
>>> build/integration test errors.
>>>
>>> Question to all (with the exception of Rupert):
>>>
>>> Are you able to run "mvn clean install" without seeing a build error?
>>> (And which environment are you using?)
>>>
>>> Cheers,
>>> Andreas
>>>
>>
>>
>
>
> --
>
> ------------------------------
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> London W6 7AN.



-- 
Fabian
http://twitter.com/fctwitt

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

Posted by Rafa Haro <rh...@zaizi.com>.

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 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, mixed mode)
>
> (maybe problems are with Java 7)
>
> Anyway, I think if there is an unclosed problem with that and Andreas
> proposes to wait until it is fixed, we may also decide to move the
> development to the branch (much important thing IMHO), keep trunk as it is
> (freezed) but still waiting for the problem to be solved before the next
> release.
>
> WDYT?
>
>
> Cheers,
> Enrico
>
>
> On 18 October 2013 10:03, Andreas Kuckartz <a....@ping.de> wrote:
>
>> 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 regarding those
>> build/integration test errors.
>>
>> Question to all (with the exception of Rupert):
>>
>> Are you able to run "mvn clean install" without seeing a build error?
>> (And which environment are you using?)
>>
>> Cheers,
>> Andreas
>>
>
>


-- 

------------------------------
This message should be regarded as confidential. If you have received this 
email in error please notify the sender and destroy it immediately. 
Statements of intent shall only become binding when confirmed in hard copy 
by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 
6440931. The Registered Office is Brook House, 229 Shepherds Bush Road, 
London W6 7AN.

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

Posted by Enrico Daga <en...@gmail.com>.

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, mixed mode)

(maybe problems are with Java 7)

Anyway, I think if there is an unclosed problem with that and Andreas
proposes to wait until it is fixed, we may also decide to move the
development to the branch (much important thing IMHO), keep trunk as it is
(freezed) but still waiting for the problem to be solved before the next
release.

WDYT?

Cheers,
Enrico

On 18 October 2013 10:03, Andreas Kuckartz <a....@ping.de> wrote:

> 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 regarding those
> build/integration test errors.
>
> Question to all (with the exception of Rupert):
>
> Are you able to run "mvn clean install" without seeing a build error?
> (And which environment are you using?)
>
> Cheers,
> Andreas
>

-- 
Enrico Daga

--
http://www.enridaga.net
skype: enri-pan

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

Posted by Andreas Kuckartz <a....@ping.de>.

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 regarding those
build/integration test errors.

Question to all (with the exception of Rupert):

Are you able to run "mvn clean install" without seeing a build error?
(And which environment are you using?)

Cheers,
Andreas

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

Posted by Rupert Westenthaler <ru...@gmail.com>.

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 the JIRA issue).
* 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.

So from my side closing the trunk today in the evening should be fine

best
Rupert

On Thu, Oct 17, 2013 at 12:19 PM, Andreas Kuckartz <a....@ping.de> wrote:
> Fabian Christ:
>> we have been discussing this for a while but now it is time for action ;)
>>
>> I would like to close the commit window for the last 0.x release this
>> Friday. Please, make sure that you have committed your pending changes
>> to the trunk.
>>
>> I will create a release branch from the trunk and cut the release in
>> the upcoming days. In parallel the ng-branch will become the new trunk
>> for further development and the then obsolete ng-branch gets removed.
>>
>> Any objections?
>
> So far I am not able to successfully execute "mvn clean build" using
> OpenJDK 7 due to integration test errors.
>
> I think that this should be resolved before the release is done.
>
> Cheers,
> Andreas

-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

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

Posted by Andreas Kuckartz <a....@ping.de>.

Fabian Christ:
> we have been discussing this for a while but now it is time for action ;)
> 
> I would like to close the commit window for the last 0.x release this
> Friday. Please, make sure that you have committed your pending changes
> to the trunk.
> 
> I will create a release branch from the trunk and cut the release in
> the upcoming days. In parallel the ng-branch will become the new trunk
> for further development and the then obsolete ng-branch gets removed.
> 
> Any objections?

So far I am not able to successfully execute "mvn clean build" using
OpenJDK 7 due to integration test errors.

I think that this should be resolved before the release is done.

Cheers,
Andreas