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/07/17 15:01:30 UTC
Stanbol Summer Term '13 release
Hi,
time has passed since our last releases at the beginning of 2013. Since new
features are under development in different branches we should fix what we
have in the trunk.
I propose to prepare a big release of the trunk with all its major
components. I would exclude the launchers and bundlelists in this release.
When that is done we should release bundlelists and launcher configurations
based on stable (released) components.
I will start to check the trunk for RAT compliance. Once everything is
checked I would create a release branch.
WDYT?
Best,
- Fabian
Re: Stanbol Summer Term '13 release
Posted by Tommaso Teofili <to...@gmail.com>.
thanks Fabian, it sounds good to me.
Tommaso
2013/7/17 Fabian Christ <ch...@googlemail.com>
> Hi,
>
> time has passed since our last releases at the beginning of 2013. Since new
> features are under development in different branches we should fix what we
> have in the trunk.
>
> I propose to prepare a big release of the trunk with all its major
> components. I would exclude the launchers and bundlelists in this release.
>
> When that is done we should release bundlelists and launcher configurations
> based on stable (released) components.
>
> I will start to check the trunk for RAT compliance. Once everything is
> checked I would create a release branch.
>
> WDYT?
>
> Best,
> - Fabian
>
Re: Stanbol Summer Term '13 release
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Fabian,
I will try to complete all tasks required for a release in this week.
The first two weeks in August I am in Portugal and will not be able to
contribute much.
I plan to commit some things to trunk (mainly refactoring of the
EntiyLinking required by the FST Linking Engine - STANBOL-1128). While
I also plan to commit a first version of the FST Linking engine this
week it should not be part of the release, as it is still in a work in
progress state.
Fabian, if you need something specific, just ping me (Mail of IRC)
best
Rupert
On Wed, Jul 17, 2013 at 3:59 PM, Reto Bachmann-Gmür <re...@wymiwyg.com> wrote:
> On Wed, Jul 17, 2013 at 3:35 PM, Fabian Christ
> <ch...@googlemail.com> wrote:
>> Hi,
>>
>> okay, so I can proceed to make trunk technically releasable. The other task
>> is to review all resolved Jira issues and prepare the release docs. This
>> will take a couple of days anyway.
>>
>> Do I understand correctly that you would like to make the ng branch the new
>> trunk after the release? Sounds reasonable to me and switching to
>> 1.0-SNAPSHOT, too.
>
> Yes I think that would be the easiest was to go. trunk becomes
> branches/pre-1 and commons-ng become trunk.
>
> Cheers,
> Reto
>
>>
>> Best,
>> - Fabian
>> Am 17.07.2013 15:22 schrieb "Reto Bachmann-Gmür" <re...@wymiwyg.com>:
>>
>>> Hi,
>>>
>>> Right now I'm porting the enhancer to ng. With that we would have the
>>> two most heavily developed components in ng and I think we should move
>>> the ongoing development to the code in that branch.
>>>
>>> So I wanted to propose this after finishing the current porting. This
>>> would mean to have one last release from the pre-ng code and then
>>> switch to the ng-branch and globaly to 1.0.0-SNAPSHOT versions.
>>>
>>> I'd suggest to wait a couple of days till we have the enhancer in ng
>>> and maybe Enrico ported one more component as to be able to see if we
>>> can coordinate this release with the switch to ng.
>>>
>>> Cheers,
>>> Reto
>>>
>>> On Wed, Jul 17, 2013 at 3:01 PM, Fabian Christ
>>> <ch...@googlemail.com> wrote:
>>> > Hi,
>>> >
>>> > time has passed since our last releases at the beginning of 2013. Since
>>> new
>>> > features are under development in different branches we should fix what
>>> we
>>> > have in the trunk.
>>> >
>>> > I propose to prepare a big release of the trunk with all its major
>>> > components. I would exclude the launchers and bundlelists in this
>>> release.
>>> >
>>> > When that is done we should release bundlelists and launcher
>>> configurations
>>> > based on stable (released) components.
>>> >
>>> > I will start to check the trunk for RAT compliance. Once everything is
>>> > checked I would create a release branch.
>>> >
>>> > WDYT?
>>> >
>>> > Best,
>>> > - Fabian
>>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: Stanbol Summer Term '13 release
Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.
On Wed, Jul 17, 2013 at 3:35 PM, Fabian Christ
<ch...@googlemail.com> wrote:
> Hi,
>
> okay, so I can proceed to make trunk technically releasable. The other task
> is to review all resolved Jira issues and prepare the release docs. This
> will take a couple of days anyway.
>
> Do I understand correctly that you would like to make the ng branch the new
> trunk after the release? Sounds reasonable to me and switching to
> 1.0-SNAPSHOT, too.
Yes I think that would be the easiest was to go. trunk becomes
branches/pre-1 and commons-ng become trunk.
Cheers,
Reto
>
> Best,
> - Fabian
> Am 17.07.2013 15:22 schrieb "Reto Bachmann-Gmür" <re...@wymiwyg.com>:
>
>> Hi,
>>
>> Right now I'm porting the enhancer to ng. With that we would have the
>> two most heavily developed components in ng and I think we should move
>> the ongoing development to the code in that branch.
>>
>> So I wanted to propose this after finishing the current porting. This
>> would mean to have one last release from the pre-ng code and then
>> switch to the ng-branch and globaly to 1.0.0-SNAPSHOT versions.
>>
>> I'd suggest to wait a couple of days till we have the enhancer in ng
>> and maybe Enrico ported one more component as to be able to see if we
>> can coordinate this release with the switch to ng.
>>
>> Cheers,
>> Reto
>>
>> On Wed, Jul 17, 2013 at 3:01 PM, Fabian Christ
>> <ch...@googlemail.com> wrote:
>> > Hi,
>> >
>> > time has passed since our last releases at the beginning of 2013. Since
>> new
>> > features are under development in different branches we should fix what
>> we
>> > have in the trunk.
>> >
>> > I propose to prepare a big release of the trunk with all its major
>> > components. I would exclude the launchers and bundlelists in this
>> release.
>> >
>> > When that is done we should release bundlelists and launcher
>> configurations
>> > based on stable (released) components.
>> >
>> > I will start to check the trunk for RAT compliance. Once everything is
>> > checked I would create a release branch.
>> >
>> > WDYT?
>> >
>> > Best,
>> > - Fabian
>>
Re: Stanbol Summer Term '13 release
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
okay, so I can proceed to make trunk technically releasable. The other task
is to review all resolved Jira issues and prepare the release docs. This
will take a couple of days anyway.
Do I understand correctly that you would like to make the ng branch the new
trunk after the release? Sounds reasonable to me and switching to
1.0-SNAPSHOT, too.
Best,
- Fabian
Am 17.07.2013 15:22 schrieb "Reto Bachmann-Gmür" <re...@wymiwyg.com>:
> Hi,
>
> Right now I'm porting the enhancer to ng. With that we would have the
> two most heavily developed components in ng and I think we should move
> the ongoing development to the code in that branch.
>
> So I wanted to propose this after finishing the current porting. This
> would mean to have one last release from the pre-ng code and then
> switch to the ng-branch and globaly to 1.0.0-SNAPSHOT versions.
>
> I'd suggest to wait a couple of days till we have the enhancer in ng
> and maybe Enrico ported one more component as to be able to see if we
> can coordinate this release with the switch to ng.
>
> Cheers,
> Reto
>
> On Wed, Jul 17, 2013 at 3:01 PM, Fabian Christ
> <ch...@googlemail.com> wrote:
> > Hi,
> >
> > time has passed since our last releases at the beginning of 2013. Since
> new
> > features are under development in different branches we should fix what
> we
> > have in the trunk.
> >
> > I propose to prepare a big release of the trunk with all its major
> > components. I would exclude the launchers and bundlelists in this
> release.
> >
> > When that is done we should release bundlelists and launcher
> configurations
> > based on stable (released) components.
> >
> > I will start to check the trunk for RAT compliance. Once everything is
> > checked I would create a release branch.
> >
> > WDYT?
> >
> > Best,
> > - Fabian
>
Re: Stanbol Summer Term '13 release
Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.
Hi,
Right now I'm porting the enhancer to ng. With that we would have the
two most heavily developed components in ng and I think we should move
the ongoing development to the code in that branch.
So I wanted to propose this after finishing the current porting. This
would mean to have one last release from the pre-ng code and then
switch to the ng-branch and globaly to 1.0.0-SNAPSHOT versions.
I'd suggest to wait a couple of days till we have the enhancer in ng
and maybe Enrico ported one more component as to be able to see if we
can coordinate this release with the switch to ng.
Cheers,
Reto
On Wed, Jul 17, 2013 at 3:01 PM, Fabian Christ
<ch...@googlemail.com> wrote:
> Hi,
>
> time has passed since our last releases at the beginning of 2013. Since new
> features are under development in different branches we should fix what we
> have in the trunk.
>
> I propose to prepare a big release of the trunk with all its major
> components. I would exclude the launchers and bundlelists in this release.
>
> When that is done we should release bundlelists and launcher configurations
> based on stable (released) components.
>
> I will start to check the trunk for RAT compliance. Once everything is
> checked I would create a release branch.
>
> WDYT?
>
> Best,
> - Fabian