On Tue, 19 May 2009, Chris Friesen wrote: > > The tagging would be done only by the "official" build process (which > pulls from an "official" repository), not by each designer. Typically > the official builds would be done weekly, more frequently if requested. Well, you can tag when you do that official build. Do you really do "official" builds from all branches? That sounds a bit insane. Remember: you don't have to tag whatever is the "top" - tagging can happen later. Tagging at build-time is perfectly fine. In fact, I'd suggest going even further. Don't tag the source branch when you build - tag it after it has passed whatever testing you do (I hope you _do_ have some extensive test-suite before release), and as you actually make it public (or whatever you do). Only at _that_ point, tag the tree with "release-$branch-$date" or something like that. Remember: you don't have to tag the top-of branch. You can tag any commit, after-the-fact. So even if you've done other development since, just make sure to tag the commit you actually built and tested. Linus -- 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