You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Reto Bachmann-Gmür <re...@apache.org> on 2012/04/16 16:28:46 UTC
Versioning in trunk and RCs
Hello
I've just adapted some sources of a project depending on Stanbol as I
noticed that InMemoryContentItem was replaced. Now I see that while this
change happened in 0.9-incubating-SNAPSHOT is it not part of the candidate
0.9-incubating release candidate. Shouldn't the version in trunk be update
for changes that do not yet make it into the released version? I think when
one is working on the latest snapshot when a version is released they
should only need to release SNAPSHOT from the dependency versions.
Cheers,
Reto
On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <christ.fabian@googlemail.com
> wrote:
> Hi,
>
> This is the sixth candidate to release Apache Stanbol 0.9.0-incubating.
>
> Please vote for releasing
> Apache Stanbol 0.9.0-incubating RC6
>
> The release is available for download at:
> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
>
> Keys are at:
> http://www.apache.org/dist/incubator/stanbol/KEYS
>
> Release tag is:
> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
>
> This release covers 405 resolved issues marked in JIRA as fixed for
> 0.9.0-incubating.
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
>
> Compared to the RC5 the RC6 fixes the following issues:
> https://issues.apache.org/jira/browse/STANBOL-557
> https://issues.apache.org/jira/browse/STANBOL-558
> https://issues.apache.org/jira/browse/STANBOL-566
>
> This vote is open for at least 72 hours.
>
> Best,
> - Fabian
>
> --
> Fabian
> http://twitter.com/fctwitt
>
Re: Versioning in trunk and RCs
Posted by Reto Bachmann-Gmür <re...@apache.org>.
On Wed, Apr 18, 2012 at 3:59 PM, Fabian Christ <christ.fabian@googlemail.com
> wrote:
> Hi Reto,
>
> thanks for the info. IMO we do the same in Stanbol so maybe you are
> right and we can also use the release plugin for this. Which Maven
> command do you use in Clerezza to build the release?
>
> Is it at the top level just:
> mvn release:prepare
>
Yes, IIRC that was all. For testing stuff I think I had to use
-Prelease,apache-release.
Cheers,
Reto
>
> Best,
> - Fabian
>
> Am 18. April 2012 15:54 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> > Hi Fabian
> >
> > The release plugin doesn't require to do many single releases, it can be
> > applied on a reactor pom. For Clerezza I've been using the maven release
> > plugin to create a big source release. We have a profile in the parent
> that
> > contained only the modules that are to be part of the relase. The apache
> > parent pom references an assembly descriptor that created the source
> bundle
> > (part of the apache-release profile), however as this didn't match the
> > clerezza source structure we had to add our own
> source-assembly-descriptor.
> >
> > Cheers,
> > Reto
> >
> > On Mon, Apr 16, 2012 at 5:05 PM, Fabian Christ <
> christ.fabian@googlemail.com
> >> wrote:
> >
> >> Hi Reto,
> >>
> >> you are right, but we are not using the release plugin for the
> >> 0.9.0-incubating release. We tried so far to create one big source
> >> release and not many single releases of each component. For the big
> >> source release packaging the release plugin does not help.
> >>
> >> For the future I would like to be able to do big source releases for
> >> major changes and incremental smaller releases of single components
> >> using the release plugin. That would be nice ;)
> >>
> >> Best,
> >> - Fabian
> >>
> >> Am 16. April 2012 16:58 schrieb Reto Bachmann-Gmür <
> me@farewellutopia.com
> >> >:
> >> > I agree with 0.10. But doesn't usually the release plugin take care
> about
> >> > updating the version in svn to the next SNAPSHOT version?
> >> >
> >> > Reto
> >> >
> >> > On Mon, Apr 16, 2012 at 4:55 PM, Fabian Christ <
> >> christ.fabian@googlemail.com
> >> >> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I have already created
> >> >>
> >> >> https://issues.apache.org/jira/browse/STANBOL-552
> >> >>
> >> >> for this. We should update our POMs in the trunk.
> >> >>
> >> >> - Fabian
> >> >>
> >> >> Am 16. April 2012 16:28 schrieb Reto Bachmann-Gmür <reto@apache.org
> >:
> >> >> > Hello
> >> >> >
> >> >> > I've just adapted some sources of a project depending on Stanbol
> as I
> >> >> > noticed that InMemoryContentItem was replaced. Now I see that while
> >> this
> >> >> > change happened in 0.9-incubating-SNAPSHOT is it not part of the
> >> >> candidate
> >> >> > 0.9-incubating release candidate. Shouldn't the version in trunk be
> >> >> update
> >> >> > for changes that do not yet make it into the released version? I
> think
> >> >> when
> >> >> > one is working on the latest snapshot when a version is released
> they
> >> >> > should only need to release SNAPSHOT from the dependency versions.
> >> >> >
> >> >> > Cheers,
> >> >> > Reto
> >> >> >
> >> >> > On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <
> >> >> christ.fabian@googlemail.com
> >> >> >> wrote:
> >> >> >
> >> >> >> Hi,
> >> >> >>
> >> >> >> This is the sixth candidate to release Apache Stanbol
> >> 0.9.0-incubating.
> >> >> >>
> >> >> >> Please vote for releasing
> >> >> >> Apache Stanbol 0.9.0-incubating RC6
> >> >> >>
> >> >> >> The release is available for download at:
> >> >> >>
> >> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
> >> >> >>
> >> >> >> Keys are at:
> >> >> >> http://www.apache.org/dist/incubator/stanbol/KEYS
> >> >> >>
> >> >> >> Release tag is:
> >> >> >>
> >> >>
> >>
> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
> >> >> >>
> >> >> >> This release covers 405 resolved issues marked in JIRA as fixed
> for
> >> >> >> 0.9.0-incubating.
> >> >> >>
> >> >> >>
> >> >>
> >>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
> >> >> >>
> >> >> >> Compared to the RC5 the RC6 fixes the following issues:
> >> >> >> https://issues.apache.org/jira/browse/STANBOL-557
> >> >> >> https://issues.apache.org/jira/browse/STANBOL-558
> >> >> >> https://issues.apache.org/jira/browse/STANBOL-566
> >> >> >>
> >> >> >> This vote is open for at least 72 hours.
> >> >> >>
> >> >> >> Best,
> >> >> >> - Fabian
> >> >> >>
> >> >> >> --
> >> >> >> Fabian
> >> >> >> http://twitter.com/fctwitt
> >> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Fabian
> >> >> http://twitter.com/fctwitt
> >> >>
> >>
> >>
> >>
> >> --
> >> Fabian
> >> http://twitter.com/fctwitt
> >>
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>
Re: Versioning in trunk and RCs
Posted by Fabian Christ <ch...@googlemail.com>.
Hi Reto,
thanks for the info. IMO we do the same in Stanbol so maybe you are
right and we can also use the release plugin for this. Which Maven
command do you use in Clerezza to build the release?
Is it at the top level just:
mvn release:prepare
Best,
- Fabian
Am 18. April 2012 15:54 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> Hi Fabian
>
> The release plugin doesn't require to do many single releases, it can be
> applied on a reactor pom. For Clerezza I've been using the maven release
> plugin to create a big source release. We have a profile in the parent that
> contained only the modules that are to be part of the relase. The apache
> parent pom references an assembly descriptor that created the source bundle
> (part of the apache-release profile), however as this didn't match the
> clerezza source structure we had to add our own source-assembly-descriptor.
>
> Cheers,
> Reto
>
> On Mon, Apr 16, 2012 at 5:05 PM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> Hi Reto,
>>
>> you are right, but we are not using the release plugin for the
>> 0.9.0-incubating release. We tried so far to create one big source
>> release and not many single releases of each component. For the big
>> source release packaging the release plugin does not help.
>>
>> For the future I would like to be able to do big source releases for
>> major changes and incremental smaller releases of single components
>> using the release plugin. That would be nice ;)
>>
>> Best,
>> - Fabian
>>
>> Am 16. April 2012 16:58 schrieb Reto Bachmann-Gmür <me@farewellutopia.com
>> >:
>> > I agree with 0.10. But doesn't usually the release plugin take care about
>> > updating the version in svn to the next SNAPSHOT version?
>> >
>> > Reto
>> >
>> > On Mon, Apr 16, 2012 at 4:55 PM, Fabian Christ <
>> christ.fabian@googlemail.com
>> >> wrote:
>> >
>> >> Hi,
>> >>
>> >> I have already created
>> >>
>> >> https://issues.apache.org/jira/browse/STANBOL-552
>> >>
>> >> for this. We should update our POMs in the trunk.
>> >>
>> >> - Fabian
>> >>
>> >> Am 16. April 2012 16:28 schrieb Reto Bachmann-Gmür <re...@apache.org>:
>> >> > Hello
>> >> >
>> >> > I've just adapted some sources of a project depending on Stanbol as I
>> >> > noticed that InMemoryContentItem was replaced. Now I see that while
>> this
>> >> > change happened in 0.9-incubating-SNAPSHOT is it not part of the
>> >> candidate
>> >> > 0.9-incubating release candidate. Shouldn't the version in trunk be
>> >> update
>> >> > for changes that do not yet make it into the released version? I think
>> >> when
>> >> > one is working on the latest snapshot when a version is released they
>> >> > should only need to release SNAPSHOT from the dependency versions.
>> >> >
>> >> > Cheers,
>> >> > Reto
>> >> >
>> >> > On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <
>> >> christ.fabian@googlemail.com
>> >> >> wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> This is the sixth candidate to release Apache Stanbol
>> 0.9.0-incubating.
>> >> >>
>> >> >> Please vote for releasing
>> >> >> Apache Stanbol 0.9.0-incubating RC6
>> >> >>
>> >> >> The release is available for download at:
>> >> >>
>> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
>> >> >>
>> >> >> Keys are at:
>> >> >> http://www.apache.org/dist/incubator/stanbol/KEYS
>> >> >>
>> >> >> Release tag is:
>> >> >>
>> >>
>> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
>> >> >>
>> >> >> This release covers 405 resolved issues marked in JIRA as fixed for
>> >> >> 0.9.0-incubating.
>> >> >>
>> >> >>
>> >>
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
>> >> >>
>> >> >> Compared to the RC5 the RC6 fixes the following issues:
>> >> >> https://issues.apache.org/jira/browse/STANBOL-557
>> >> >> https://issues.apache.org/jira/browse/STANBOL-558
>> >> >> https://issues.apache.org/jira/browse/STANBOL-566
>> >> >>
>> >> >> This vote is open for at least 72 hours.
>> >> >>
>> >> >> Best,
>> >> >> - Fabian
>> >> >>
>> >> >> --
>> >> >> Fabian
>> >> >> http://twitter.com/fctwitt
>> >> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Fabian
>> >> http://twitter.com/fctwitt
>> >>
>>
>>
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>
--
Fabian
http://twitter.com/fctwitt
Re: Versioning in trunk and RCs
Posted by Reto Bachmann-Gmür <re...@apache.org>.
Hi Fabian
The release plugin doesn't require to do many single releases, it can be
applied on a reactor pom. For Clerezza I've been using the maven release
plugin to create a big source release. We have a profile in the parent that
contained only the modules that are to be part of the relase. The apache
parent pom references an assembly descriptor that created the source bundle
(part of the apache-release profile), however as this didn't match the
clerezza source structure we had to add our own source-assembly-descriptor.
Cheers,
Reto
On Mon, Apr 16, 2012 at 5:05 PM, Fabian Christ <christ.fabian@googlemail.com
> wrote:
> Hi Reto,
>
> you are right, but we are not using the release plugin for the
> 0.9.0-incubating release. We tried so far to create one big source
> release and not many single releases of each component. For the big
> source release packaging the release plugin does not help.
>
> For the future I would like to be able to do big source releases for
> major changes and incremental smaller releases of single components
> using the release plugin. That would be nice ;)
>
> Best,
> - Fabian
>
> Am 16. April 2012 16:58 schrieb Reto Bachmann-Gmür <me@farewellutopia.com
> >:
> > I agree with 0.10. But doesn't usually the release plugin take care about
> > updating the version in svn to the next SNAPSHOT version?
> >
> > Reto
> >
> > On Mon, Apr 16, 2012 at 4:55 PM, Fabian Christ <
> christ.fabian@googlemail.com
> >> wrote:
> >
> >> Hi,
> >>
> >> I have already created
> >>
> >> https://issues.apache.org/jira/browse/STANBOL-552
> >>
> >> for this. We should update our POMs in the trunk.
> >>
> >> - Fabian
> >>
> >> Am 16. April 2012 16:28 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> >> > Hello
> >> >
> >> > I've just adapted some sources of a project depending on Stanbol as I
> >> > noticed that InMemoryContentItem was replaced. Now I see that while
> this
> >> > change happened in 0.9-incubating-SNAPSHOT is it not part of the
> >> candidate
> >> > 0.9-incubating release candidate. Shouldn't the version in trunk be
> >> update
> >> > for changes that do not yet make it into the released version? I think
> >> when
> >> > one is working on the latest snapshot when a version is released they
> >> > should only need to release SNAPSHOT from the dependency versions.
> >> >
> >> > Cheers,
> >> > Reto
> >> >
> >> > On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <
> >> christ.fabian@googlemail.com
> >> >> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> This is the sixth candidate to release Apache Stanbol
> 0.9.0-incubating.
> >> >>
> >> >> Please vote for releasing
> >> >> Apache Stanbol 0.9.0-incubating RC6
> >> >>
> >> >> The release is available for download at:
> >> >>
> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
> >> >>
> >> >> Keys are at:
> >> >> http://www.apache.org/dist/incubator/stanbol/KEYS
> >> >>
> >> >> Release tag is:
> >> >>
> >>
> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
> >> >>
> >> >> This release covers 405 resolved issues marked in JIRA as fixed for
> >> >> 0.9.0-incubating.
> >> >>
> >> >>
> >>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
> >> >>
> >> >> Compared to the RC5 the RC6 fixes the following issues:
> >> >> https://issues.apache.org/jira/browse/STANBOL-557
> >> >> https://issues.apache.org/jira/browse/STANBOL-558
> >> >> https://issues.apache.org/jira/browse/STANBOL-566
> >> >>
> >> >> This vote is open for at least 72 hours.
> >> >>
> >> >> Best,
> >> >> - Fabian
> >> >>
> >> >> --
> >> >> Fabian
> >> >> http://twitter.com/fctwitt
> >> >>
> >>
> >>
> >>
> >> --
> >> Fabian
> >> http://twitter.com/fctwitt
> >>
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>
Re: Versioning in trunk and RCs
Posted by Fabian Christ <ch...@googlemail.com>.
Hi Reto,
you are right, but we are not using the release plugin for the
0.9.0-incubating release. We tried so far to create one big source
release and not many single releases of each component. For the big
source release packaging the release plugin does not help.
For the future I would like to be able to do big source releases for
major changes and incremental smaller releases of single components
using the release plugin. That would be nice ;)
Best,
- Fabian
Am 16. April 2012 16:58 schrieb Reto Bachmann-Gmür <me...@farewellutopia.com>:
> I agree with 0.10. But doesn't usually the release plugin take care about
> updating the version in svn to the next SNAPSHOT version?
>
> Reto
>
> On Mon, Apr 16, 2012 at 4:55 PM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> Hi,
>>
>> I have already created
>>
>> https://issues.apache.org/jira/browse/STANBOL-552
>>
>> for this. We should update our POMs in the trunk.
>>
>> - Fabian
>>
>> Am 16. April 2012 16:28 schrieb Reto Bachmann-Gmür <re...@apache.org>:
>> > Hello
>> >
>> > I've just adapted some sources of a project depending on Stanbol as I
>> > noticed that InMemoryContentItem was replaced. Now I see that while this
>> > change happened in 0.9-incubating-SNAPSHOT is it not part of the
>> candidate
>> > 0.9-incubating release candidate. Shouldn't the version in trunk be
>> update
>> > for changes that do not yet make it into the released version? I think
>> when
>> > one is working on the latest snapshot when a version is released they
>> > should only need to release SNAPSHOT from the dependency versions.
>> >
>> > Cheers,
>> > Reto
>> >
>> > On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <
>> christ.fabian@googlemail.com
>> >> wrote:
>> >
>> >> Hi,
>> >>
>> >> This is the sixth candidate to release Apache Stanbol 0.9.0-incubating.
>> >>
>> >> Please vote for releasing
>> >> Apache Stanbol 0.9.0-incubating RC6
>> >>
>> >> The release is available for download at:
>> >> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
>> >>
>> >> Keys are at:
>> >> http://www.apache.org/dist/incubator/stanbol/KEYS
>> >>
>> >> Release tag is:
>> >>
>> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
>> >>
>> >> This release covers 405 resolved issues marked in JIRA as fixed for
>> >> 0.9.0-incubating.
>> >>
>> >>
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
>> >>
>> >> Compared to the RC5 the RC6 fixes the following issues:
>> >> https://issues.apache.org/jira/browse/STANBOL-557
>> >> https://issues.apache.org/jira/browse/STANBOL-558
>> >> https://issues.apache.org/jira/browse/STANBOL-566
>> >>
>> >> This vote is open for at least 72 hours.
>> >>
>> >> Best,
>> >> - Fabian
>> >>
>> >> --
>> >> Fabian
>> >> http://twitter.com/fctwitt
>> >>
>>
>>
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>
--
Fabian
http://twitter.com/fctwitt
Re: Versioning in trunk and RCs
Posted by Reto Bachmann-Gmür <me...@farewellutopia.com>.
I agree with 0.10. But doesn't usually the release plugin take care about
updating the version in svn to the next SNAPSHOT version?
Reto
On Mon, Apr 16, 2012 at 4:55 PM, Fabian Christ <christ.fabian@googlemail.com
> wrote:
> Hi,
>
> I have already created
>
> https://issues.apache.org/jira/browse/STANBOL-552
>
> for this. We should update our POMs in the trunk.
>
> - Fabian
>
> Am 16. April 2012 16:28 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> > Hello
> >
> > I've just adapted some sources of a project depending on Stanbol as I
> > noticed that InMemoryContentItem was replaced. Now I see that while this
> > change happened in 0.9-incubating-SNAPSHOT is it not part of the
> candidate
> > 0.9-incubating release candidate. Shouldn't the version in trunk be
> update
> > for changes that do not yet make it into the released version? I think
> when
> > one is working on the latest snapshot when a version is released they
> > should only need to release SNAPSHOT from the dependency versions.
> >
> > Cheers,
> > Reto
> >
> > On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <
> christ.fabian@googlemail.com
> >> wrote:
> >
> >> Hi,
> >>
> >> This is the sixth candidate to release Apache Stanbol 0.9.0-incubating.
> >>
> >> Please vote for releasing
> >> Apache Stanbol 0.9.0-incubating RC6
> >>
> >> The release is available for download at:
> >> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
> >>
> >> Keys are at:
> >> http://www.apache.org/dist/incubator/stanbol/KEYS
> >>
> >> Release tag is:
> >>
> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
> >>
> >> This release covers 405 resolved issues marked in JIRA as fixed for
> >> 0.9.0-incubating.
> >>
> >>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
> >>
> >> Compared to the RC5 the RC6 fixes the following issues:
> >> https://issues.apache.org/jira/browse/STANBOL-557
> >> https://issues.apache.org/jira/browse/STANBOL-558
> >> https://issues.apache.org/jira/browse/STANBOL-566
> >>
> >> This vote is open for at least 72 hours.
> >>
> >> Best,
> >> - Fabian
> >>
> >> --
> >> Fabian
> >> http://twitter.com/fctwitt
> >>
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>
Re: Versioning in trunk and RCs
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
I have already created
https://issues.apache.org/jira/browse/STANBOL-552
for this. We should update our POMs in the trunk.
- Fabian
Am 16. April 2012 16:28 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> Hello
>
> I've just adapted some sources of a project depending on Stanbol as I
> noticed that InMemoryContentItem was replaced. Now I see that while this
> change happened in 0.9-incubating-SNAPSHOT is it not part of the candidate
> 0.9-incubating release candidate. Shouldn't the version in trunk be update
> for changes that do not yet make it into the released version? I think when
> one is working on the latest snapshot when a version is released they
> should only need to release SNAPSHOT from the dependency versions.
>
> Cheers,
> Reto
>
> On Mon, Apr 2, 2012 at 11:24 AM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> Hi,
>>
>> This is the sixth candidate to release Apache Stanbol 0.9.0-incubating.
>>
>> Please vote for releasing
>> Apache Stanbol 0.9.0-incubating RC6
>>
>> The release is available for download at:
>> http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC6/
>>
>> Keys are at:
>> http://www.apache.org/dist/incubator/stanbol/KEYS
>>
>> Release tag is:
>> https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating
>>
>> This release covers 405 resolved issues marked in JIRA as fixed for
>> 0.9.0-incubating.
>>
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12319391
>>
>> Compared to the RC5 the RC6 fixes the following issues:
>> https://issues.apache.org/jira/browse/STANBOL-557
>> https://issues.apache.org/jira/browse/STANBOL-558
>> https://issues.apache.org/jira/browse/STANBOL-566
>>
>> This vote is open for at least 72 hours.
>>
>> Best,
>> - Fabian
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>
--
Fabian
http://twitter.com/fctwitt