We're going through the same thing at work right now. We've looked at three approaches:
- Home-grown setup based on the ideas in this post.
- SubGit
- Atlassian Stash + Subgit plugin
We're already using in-house JIRA/GreenHopper instances extensively, and the first two solutions are too 'fiddly' for our liking, so we plan to try Stash + SubGit in the new year. (No affiliation, just been circling around solutions to this problem for awhile, and this one looks the most promising.)
So, to answer your question: the work flow you describe is certainly possible with git-svn
, but... it may be more trouble than it's worth unless you have a very small team (three or four developers) who are all git and svn ninjas. For our 30-person team of very mixed backgrounds and skill sets, we just weren't comfortable trying to set up a transparent git-svn bridge on our own.