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 2013/10/15 20:36:51 UTC
ng-branch, commits and release
Hi,
There hasn't been a lot of discussion regarding the ng-branch. Maybe
misinterpreting silence as consent I assumed we would agree that:
- We will have the last 0.X release soon (I assumed "Summer 13" to refer to
the one in the northern hemisphere) from trunk
- After that commongs-ng will become the new trunk
- The modules that are still actively developed are moved to ng
As a consequences of this the commits to trunk should be limited to what
really should be part of the next release. However there have been lots of
commits (almost all from Rupert) into the trunk branch. Some of the
commits, like today's issue and patch to provide a Sesame based entityhub
model for sesame definitively sound like new features than like pre-release
polishing.
With rules, ontologymanager, reasoning, having been added during the last
weeks (thanks Enrico) the ng-branch is quite complete.
How shall we proceed?
Cheers,
Reto
Re: ng-branch, commits and release
Posted by Reto Bachmann-Gmür <re...@wymiwyg.com>.
Ok, that give me an incentive to port the integration test by friday.
Cheers,
Reto
On Wed, Oct 16, 2013 at 10:09 AM, Fabian Christ <
christ.fabian@googlemail.com> wrote:
> Thinking about it - what about defining that this Friday is the end of
> development for the 0.x release in trunk. This would mean that I would
> create a release branch by end of business on Friday. Then the
> ng-branch could directly become the new trunk.
>
> 2013/10/16 Fabian Christ <ch...@googlemail.com>:
> > Hi Reto,
> >
> > you are right that we had that consensus. The missing release is my
> > fault as I do not find the time to cut it. Anyway, the trunk was once
> > already in a releasable state but I have to catch up after the recent
> > commits.
> >
> > So, how should we proceed to have a hard deadline for the trunk? Then
> > we should create a release branch from trunk for the last 0.x release
> > and make the ng-branch the new trunk.
> >
> > Hopefully, I will have time on Friday to have a closer look at the
> > trunk and proceed with release preparation. If there is anybody who
> > has the time and the willing to help or even to do the release, please
> > do not hesitate to take action.
> >
> > Best,
> > - Fabian
> >
> > 2013/10/15 Reto Bachmann-Gmür <re...@apache.org>:
> >> Hi,
> >>
> >> There hasn't been a lot of discussion regarding the ng-branch. Maybe
> >> misinterpreting silence as consent I assumed we would agree that:
> >>
> >> - We will have the last 0.X release soon (I assumed "Summer 13" to
> refer to
> >> the one in the northern hemisphere) from trunk
> >> - After that commongs-ng will become the new trunk
> >> - The modules that are still actively developed are moved to ng
> >>
> >> As a consequences of this the commits to trunk should be limited to what
> >> really should be part of the next release. However there have been lots
> of
> >> commits (almost all from Rupert) into the trunk branch. Some of the
> >> commits, like today's issue and patch to provide a Sesame based
> entityhub
> >> model for sesame definitively sound like new features than like
> pre-release
> >> polishing.
> >>
> >> With rules, ontologymanager, reasoning, having been added during the
> last
> >> weeks (thanks Enrico) the ng-branch is quite complete.
> >>
> >> How shall we proceed?
> >>
> >> Cheers,
> >> Reto
> >
> >
> >
> > --
> > Fabian
> > http://twitter.com/fctwitt
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>
Re: ng-branch, commits and release
Posted by Fabian Christ <ch...@googlemail.com>.
Thinking about it - what about defining that this Friday is the end of
development for the 0.x release in trunk. This would mean that I would
create a release branch by end of business on Friday. Then the
ng-branch could directly become the new trunk.
2013/10/16 Fabian Christ <ch...@googlemail.com>:
> Hi Reto,
>
> you are right that we had that consensus. The missing release is my
> fault as I do not find the time to cut it. Anyway, the trunk was once
> already in a releasable state but I have to catch up after the recent
> commits.
>
> So, how should we proceed to have a hard deadline for the trunk? Then
> we should create a release branch from trunk for the last 0.x release
> and make the ng-branch the new trunk.
>
> Hopefully, I will have time on Friday to have a closer look at the
> trunk and proceed with release preparation. If there is anybody who
> has the time and the willing to help or even to do the release, please
> do not hesitate to take action.
>
> Best,
> - Fabian
>
> 2013/10/15 Reto Bachmann-Gmür <re...@apache.org>:
>> Hi,
>>
>> There hasn't been a lot of discussion regarding the ng-branch. Maybe
>> misinterpreting silence as consent I assumed we would agree that:
>>
>> - We will have the last 0.X release soon (I assumed "Summer 13" to refer to
>> the one in the northern hemisphere) from trunk
>> - After that commongs-ng will become the new trunk
>> - The modules that are still actively developed are moved to ng
>>
>> As a consequences of this the commits to trunk should be limited to what
>> really should be part of the next release. However there have been lots of
>> commits (almost all from Rupert) into the trunk branch. Some of the
>> commits, like today's issue and patch to provide a Sesame based entityhub
>> model for sesame definitively sound like new features than like pre-release
>> polishing.
>>
>> With rules, ontologymanager, reasoning, having been added during the last
>> weeks (thanks Enrico) the ng-branch is quite complete.
>>
>> How shall we proceed?
>>
>> Cheers,
>> Reto
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
--
Fabian
http://twitter.com/fctwitt
Re: ng-branch, commits and release
Posted by Fabian Christ <ch...@googlemail.com>.
Hi Reto,
you are right that we had that consensus. The missing release is my
fault as I do not find the time to cut it. Anyway, the trunk was once
already in a releasable state but I have to catch up after the recent
commits.
So, how should we proceed to have a hard deadline for the trunk? Then
we should create a release branch from trunk for the last 0.x release
and make the ng-branch the new trunk.
Hopefully, I will have time on Friday to have a closer look at the
trunk and proceed with release preparation. If there is anybody who
has the time and the willing to help or even to do the release, please
do not hesitate to take action.
Best,
- Fabian
2013/10/15 Reto Bachmann-Gmür <re...@apache.org>:
> Hi,
>
> There hasn't been a lot of discussion regarding the ng-branch. Maybe
> misinterpreting silence as consent I assumed we would agree that:
>
> - We will have the last 0.X release soon (I assumed "Summer 13" to refer to
> the one in the northern hemisphere) from trunk
> - After that commongs-ng will become the new trunk
> - The modules that are still actively developed are moved to ng
>
> As a consequences of this the commits to trunk should be limited to what
> really should be part of the next release. However there have been lots of
> commits (almost all from Rupert) into the trunk branch. Some of the
> commits, like today's issue and patch to provide a Sesame based entityhub
> model for sesame definitively sound like new features than like pre-release
> polishing.
>
> With rules, ontologymanager, reasoning, having been added during the last
> weeks (thanks Enrico) the ng-branch is quite complete.
>
> How shall we proceed?
>
> Cheers,
> Reto
--
Fabian
http://twitter.com/fctwitt