Mark,
Let me try to make it clearer: when I agreed to support moves to git it was on the understanding that all project moves would be done with the clear understanding that productisation branches would still be maintained in svn. I know that that is happening for some projects. I'm hoping that it's happening for all projects. That link back to svn is the one that cannot be broken.
By this do you mean that going forward all *new* productization branches must be maintained in svn, or do you just mean that we need to keep the existing ones in svn?
I'm assuming you mean the former....
Given that productization branches would be baked in the (git based) community first, we would need to port from git to svn whenever we create a maintenance branch. This would be an additional overhead that needs to be considered. Also, is the migration path from git to svn as smooth? Does anyone actually do this?
Mark: can you explain the reasoning for keeping product on svn? This should help us understand if a compromise/hybrid approach is possible.
Thanks,
Paul.