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 2011/07/18 10:49:17 UTC
Using Long Living Stable Branch?
Hi,
facing the problem that we may want to exclude some artifacts from a
release we need a way to manage this. I see the problem that at the
moment everything in trunk is aligned to be in a release. How would I
manage to exclude some artifacts and run it through Hudson? This would
change the trunk. Some integration tests may need to be disabled.
People currently working on code that will not be in the next release
may have the problem that they can't commit their stuff for the time
the trunk is freezed for the release.
I read [1] linked from [2] and I'm thinking about creating such a
stable branch for doing releases.
WDYT?
[1] http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
[2] http://incubator.apache.org/guides/releasemanagement.html#managing%20subversion
--
Fabian
Re: Using Long Living Stable Branch?
Posted by Fabian Christ <ch...@googlemail.com>.
I have checked the whole trunk using Apache RAT and added the missing headers.
See https://issues.apache.org/jira/browse/STANBOL-272
So the trunk builds and rat:check does not claim any missing headers.
rat:check is executed when you run: mvn install -Prelease
2011/7/18 Olivier Grisel <ol...@ensta.org>:
> I am +1 for doing a release branch to be able to build and test the
> release and do minor fixes (to be merged back into the trunk) without
> blocking ongoing work on the trunk.
>
> But we should first fix all release blocking issues (e.g. check the
> license headers everywhere) in the trunk. It's not fun to do svn merge
> with checkins that potentially touch every single file in the source
> tree.
>
> --
> Olivier
>
--
Fabian
Re: Using Long Living Stable Branch?
Posted by Olivier Grisel <ol...@ensta.org>.
I am +1 for doing a release branch to be able to build and test the
release and do minor fixes (to be merged back into the trunk) without
blocking ongoing work on the trunk.
But we should first fix all release blocking issues (e.g. check the
license headers everywhere) in the trunk. It's not fun to do svn merge
with checkins that potentially touch every single file in the source
tree.
--
Olivier
Re: Using Long Living Stable Branch?
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
okay I will go the profile way.
But I see two problems:
1) Integration tests are not per bundle at the moment. So disabling a
bundle in the reactor POM won't disable its integration tests.
2) Launchers are independent of the bundles that are build -> I will
open a new thread about this.
- Fabian
2011/7/18 Bertrand Delacretaz <bd...@apache.org>:
> Hi,
>
> On Mon, Jul 18, 2011 at 10:49 AM, Fabian Christ
> <ch...@googlemail.com> wrote:
>> ...facing the problem that we may want to exclude some artifacts from a
>> release we need a way to manage this. I see the problem that at the
>> moment everything in trunk is aligned to be in a release. How would I
>> manage to exclude some artifacts and run it through Hudson? This would
>> change the trunk...
>
> You could just use a Maven profile, so that be default the trunk
> builds only what's in the release.
>
>> Some integration tests may need to be disabled...
>
> Those can check if the required bundles are present (either via OSGi
> console or by making test requests), and disable themselves if not.
> The best would be for the bundles to supply their own integration
> tests, but we can probably find an intermediate solution if we don't
> have time to set this up.
>
>> People currently working on code that will not be in the next release
>> may have the problem that they can't commit their stuff for the time
>> the trunk is freezed for the release...
>
> Using Maven profiles would limit the freeze time to a minimum.
>
>>
>> I read [1] linked from [2] and I'm thinking about creating such a
>> stable branch for doing releases....
>
> I'd rather just create an svn tag when doing the release (maven
> release plugin does that anyway), and if we need a branch later we can
> always create it from that tag.
>
> -Bertrand
>
--
Fabian
Re: Using Long Living Stable Branch?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Mon, Jul 18, 2011 at 10:49 AM, Fabian Christ
<ch...@googlemail.com> wrote:
> ...facing the problem that we may want to exclude some artifacts from a
> release we need a way to manage this. I see the problem that at the
> moment everything in trunk is aligned to be in a release. How would I
> manage to exclude some artifacts and run it through Hudson? This would
> change the trunk...
You could just use a Maven profile, so that be default the trunk
builds only what's in the release.
> Some integration tests may need to be disabled...
Those can check if the required bundles are present (either via OSGi
console or by making test requests), and disable themselves if not.
The best would be for the bundles to supply their own integration
tests, but we can probably find an intermediate solution if we don't
have time to set this up.
> People currently working on code that will not be in the next release
> may have the problem that they can't commit their stuff for the time
> the trunk is freezed for the release...
Using Maven profiles would limit the freeze time to a minimum.
>
> I read [1] linked from [2] and I'm thinking about creating such a
> stable branch for doing releases....
I'd rather just create an svn tag when doing the release (maven
release plugin does that anyway), and if we need a branch later we can
always create it from that tag.
-Bertrand
Re: Using Long Living Stable Branch?
Posted by Reto Bachmann-Gmür <me...@farewellutopia.com>.
Hi Fabian,
I don't understand why it's not enough to exclude some artifacts from
the release profile in the parent pom.
Cheers,
Reto
On Mon, Jul 18, 2011 at 10:49 AM, Fabian Christ
<ch...@googlemail.com> wrote:
> Hi,
>
> facing the problem that we may want to exclude some artifacts from a
> release we need a way to manage this. I see the problem that at the
> moment everything in trunk is aligned to be in a release. How would I
> manage to exclude some artifacts and run it through Hudson? This would
> change the trunk. Some integration tests may need to be disabled.
> People currently working on code that will not be in the next release
> may have the problem that they can't commit their stuff for the time
> the trunk is freezed for the release.
>
> I read [1] linked from [2] and I'm thinking about creating such a
> stable branch for doing releases.
>
> WDYT?
>
> [1] http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
> [2] http://incubator.apache.org/guides/releasemanagement.html#managing%20subversion
>
> --
> Fabian
>