Hi,
I had a lot of interesting discussion about various distributed SCM and
subversion in the meantime. For me it looks the discussion and evalution
of distributed SCM needs some more time than just a month because the
use of such a system also can improve or at least change our development
processes. I also have the impression that both subversion and a DSCM
(git, mercurial) can serve our needs.
The situation looks like this:
We will have next week an infrastructure available where we have the
possibility to do the transition from CVS to subversion. The subversion
tool chain seem to be mature (support for all our main development
platforms), it has been tested on all these platforms also with firewall
restrictions (a test protocol matrix with benchmarks should be available
soon). A transition to subversion would address our biggest pain: branch
creation.
A switch to DSCM is the bigger and a promising step: enhancements of our
development model and style look possible, I can't list all aspects now.
But a transition to a DSCM seems to need more preparation and
development: we need to review and maybe redesign our processes, we need
a more mature system with support for all major platforms, need to think
about additional infrastructure and more things.
So I would like to suggest the following:
Evaluate the effort for a transition to subversion first, Heiner already
did some preparations for this. If this efforts seems to be reasonable
low, do the transition from CVS to subversion first in the next few months.
As a second step or in parallel keep the evaluation for alternative SCM
open, lets use face-to-face meetings on next OOoCon for a more in depth
discussion about the future developments in our process. I guess some of
you may think that with a transition from CVS to subversion this
discussion might be dead, but I definitely don't think so. The
opportunities we have with a modern SCM are to much to get ignored but
we need some time for such thought which I don't want to let get passed
by by sitting on our old CVS.
Martin
Martin Hollmichel wrote:
Hi,
I'm looking forward to play around with a git OpenOffice.org repository.
Heiner
since we are considering a new SCM for quite a while now I suggest to
set up a wiki page for gathering all the requirements we have and the
pro and cons for the single implementations.
IMHO the goal should be that we upgrade our SCM this year (or decide to
stay with CVS for longer time), but our decision should be traceable.
I could imagine such a timeline:
until Feb 15th: collect data and arguments.
until Feb 22th: come to an decision which SCM to use. Determine which
infrastructure could be used.
I then expect a ca. 3 month time frame (+- 2month from what Heiner
estimated ) to prepare the actual transition. So we would then around
June in the situation to review the status and decide about the plan
when and how to do the transition.
sorry for putting some pressure on this topic but we all feel the pain
we currently have with CVS.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
