I think that we do not have to change our development model much. If we go the git way, we'll have to change the commands we use during the work, but the behavior (at least for the external developers) will be very much the same.
It is not only the development model itself which might be impacted. We also have to consider that we use a complete integrated infrastructure nowadays, where SVN (CVS today) is closely connected to other stuff, such as Issue tracking, authentication etc. In addition, we have created lots of tools around this (EIS, L10N, ...) which have to be more or less completely renewed if we move over to a distributed SCM.
If performance of branching and tagging is the biggest issue when dealing with OOo code and Child Workspaces (that's what I hear from time to time), this will be perfectly solved by SVN.
I think we have to ask the question "which are the issues nowadays?" instead of starting evaluation of each and every SCM.
Nils --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
