On 18/02/2014 16:42, Andreas Krüger wrote:
Hello, Bill and all,
Hi Andreas,
... whereas a VCS switch would require all developers to check in
all outstanding work in a coordinated fashion or face a complex
migration of their work in progress.
Several of my colleagues use git-svn for daily migrations, as
they prefer git, but the project happens to use svn. I'm a bit
afraid you overestimate the complexity of working in both VCSs
simultaneously for a while.
On the contrary Andreas, I also suggest git-svn and it is a good
toolset, but I was saying that a jump to git as a VCS for the public
repository is not necessarily a good idea in the middle of an enforced
hosting provider switch. It is precisely because tools like git-svn
exist that the public project(s) repository can remain a Subversion
while developers can gain some of the benefits git work flow, at least
locally, but this is nothing to do with a public repository host switch.
A switch to git (or any other VCS tool) will involve a small but not
insignificant process to transfer developer identities and
transformations of tag branches to true tags etc. Whereas a switch from
BerliOS Subversion to SourceForge /w Subversion apparently has a
seamless changeover tool.
I also like GoogleCode, but would query whether it is a good fit for a
switch from BerliOS given that it doesn't directly support mailman, it
allows collaboration via GoogleGroups (requiring a Google identity) or
it can access external mailman mailing lists, but then we would have to
find a host for the mailing lists as well :(
...
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
