We're still gonna get a svn tag for the release anyhow, right?
On 3/5/12 5:29 PM, Rupert Westenthaler wrote:
On 05.03.2012, at 15:26, Fabian Christ wrote:
Hi,
I would like to create a release candidate for a first source release
of Stanbol.
As some components can not be released because they are not stable or
have some license issues, I am thinking about creating a branch and
doing the release from that branch. Otherwise we have to remove every
component that is not releasable for any reason from the default build
process.
A release branch sounds reasonable to me.
Either we keep the trunk releasable and move everything else into
another Maven profile or we have to work with branches to make
required changes and remove stuff that should not be released.
I would rather like to "remove" some existing Maven profiles as they
create some duplications (e.g. compare the pom.xml of the enhancer
and the stanbol reactor pom.xml).
Another problem: For a release all components need to get fixed
versions (without SNAPSHOT). For a big source release we can not use
the Maven release plugin for this. I have to set the versions by hand.
If we do a release from trunk, we need something like a code freeze.
By releasing from a branch people could keep working on the trunk.
What should we do?
+1 for branch because I do not like the alternatives.
Best,
- Fabian
--
Fabian
http://twitter.com/fctwitt
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"As for the charges against me, I am unconcerned. I am beyond their timid, lying
morality, and so I am beyond caring."
(Col. Walter E. Kurtz)
Not sent from my iSnobTechDevice
