Russ Brown wrote:
Hi, I've been trying to think of a git workflow that we could use to replace our current svn/svk setup without simply using git in exactly the same way that we use svn/svk. Basically, we develop, maintain and enhance a website. On the central repo is trunk which represents live, and any number of project branches. Developers don't use local branches: they check out the project branches they're working on and commit to those. Developers merge from trunk to project branch from time to time to keep them current, and when a project rolls out the branch is merged to trunk. In addition to the obvious advantages that git would give us (such as properly tracking that code author as opposed to the person who did the merge), I'm wanting to gain the following benefits: * The repository is very large (multiple gigabytes) and mirroring using svk obviously takes a lot of time and space, so I'm keen to bring that down, most likely by the developer not needing to mirror branches he doesn't care about, or by being able to throw away branches he's done with. * The repository is full of revisions that fail review (or break things) and are fixed by subsequent revisions. We'd much rather be able to have the developer fix his revisions before they get committed 'upstream' (whatever that ends up meaning). I asked earlier about the email-based model that git itself uses, and while it appears to work very well for a widely-dispersed open-source project, I think it will be too cumbersome and slow for a fast-paced internal development team who make a number of live releases every day.
We came to the same conclusion at our workplace. Email works great, but it's faster and better to just walk over to your colleague and ask what he/she thinks about something.
So, I've been thinking and have come up with this, which I'd appreciate comments about: 1. On a server we stick a git repository which contains the master branch, which represents what trunk did (i.e. the live platform). This branch contains the full history for the live platform.
A must-have for any more-than-two-developers setup, so so far so good ;-)
2. On the same server we clone that repo to create a second repository which is the developer area. In this we track master from the live repo, and also create project branches.
This isn't necessary. Branches in git are very nearly zero-cost, so having them in the same repo as the master branch won't hurt a bit. You can add an update-hook on the mothership repo to restrict access to the master branch if you like, but creating two separate repos will likely give more headache than it's worth.
3. Developers clone this developer repo, but I'd like them to be able to decide which branches they actually want to clone from that repository rather than simply cloning them all. Is this possible?
Yes, although I'd actually recommend you to clone the full repo anyway. Since the various branches are likely to share quite a lot of history the added overhead of a few extra branches will most likely be negligible. git makes even very large codebases appear small and unobtrusive. The linux kernel history since 2.6.12 contains 554853 objects and compresses down to 178MiB. I think KDE is the largest repo imported to git so far. I've forgotten the exact numbers, but everyone was very impressed, and quite surprised, at the vast difference between SVN and git storage requirements.
4. Developers create a local branch of the project they are working on and commit to that. 5. Once they think they're done, they publish their branch to the development repo and request for comments.
Using topic-branches is a much better strategy, usually, since that allows each feature to be evaluated and improved on on its own, rather than having to merge *all* of a particular developers changes just to get desirable feature X. Note that cherry-pick provides ways of doing that anyways, but in a much less elegant way, and your integrator/ release engineer will likely tear his hair out on a daily basis without topic branches.
6. If all is not well, the developer creates a new local branch and moves good revisions from his previous one to the new one, modifying things as he goes, and republishes his new branch. 7. If all is well, their works gets merged or rebased onto the main project branch, and once that's ready it gets pushed to the master and rolled to live. The developer's individual branches get deleted from the dev repo since they're no longer required.
Topic branches would work the same, basically, except they can be pushed up for review a lot faster. If all the pushing gets cumbersome, it also makes it easy to send the patches out as emails for discussion. It's usually easier to let git handle the actual code transmissions, but discussing patches in emails works quite well if it's intended for a wider audience.
8. From time to time the master branch gets merged to the project branches. Developer's local branches can be rebased against the project branch as they please.
criss-cross merging can turn kinda nasty though, as you may have a hard time finding *the* common point when you run into that rogue merge with conflict markers everywhere (it happens for everyone sooner or later). I'd suggest you rebase the developer/topic branches onto master with regular intervals instead. -- Andreas Ericsson andreas.ericsson@xxxxxx OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
