Hi there,
So, to avoid breaking the trunk while still being able to proceed in
adding commons-compress features based on the current 1.0-SNAPSHOT,
I'd like to create a TIKA-204 development branch in svn. This branch
would be used only for TIKA-204 changes, and would be merged back to
trunk as soon as commons-compress 1.0 is out. The branch would use the
merge tracking feature in Subversion 1.5.
Any objections to this plan?
I think this is the best idea to handle such a situation and the merge
tracking will took over the part to write down the revision numbers
which will be merge later from that branch...
BTW: Not the branch will use the merge tracking feature Subversion
It is available starting with SVN 1.5...;-)
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
