Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Date: Tue, 12 Feb 2013 18:00:58 +0100
Message-ID: 
 <CALvhUEWubaL7gMQGwbE2-EAq4XJDgU2J-7d2UwCc8MWgOK=bPQ@mail.gmail.com>
Subject: releasing individual modules and versionig
From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= <reto@apache.org>
To: clerezza-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hallo

We have already been discussing this once:
http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201203.mbox/%3CCAEWfVJkK4Czkwy+w3afUoKOB8i+00e4_dyQ_-2WsT1eeqZDxKQ@mail.gmail.com%3E

Now also after having more experience with the stanbol approach I
would like to suggest the following:

1) The dependency management does not contain internal dependencies
2) All modules in trunk depend on the latest versions of the modules
in trunk, this is achieved by regularly running the mvn dependency
plugin
3) before modules are relased they are copied to a branch and the
trunk snapshot-version is increased
4) In the branch the module the dependencies to modules that are not
part of the released are switched back to the latest released version
(if incompatibilities become manifest the other modules are added to
the release branch)
5) a release is prepared on the release branch
6) vote

The idea is to reduce to effort of developing in trunk whithout having
to worry about dependencies while making it straight forward to
release only a part of the modules.


WDYT?

Cheers,
Reto