posts - 4238, comments - 3946, trackbacks - 370

My Links

News



Subscribe Subscribe

image image image





This is my personal weblog. These postings are provided 'AS IS' with no warranties, and confer no rights. The views expressed on this weblog are mine alone and do not necessarily reflect the views of my employer.

Licenza Creative Commons

Tag Cloud

Archives

Post Categories

Un post di Joel su come gestire il sorgente in progetti grossi...

Leggetelo: 

Of all the things broken at Microsoft, the way they use source control on the Windows team is not one of them.

...cut...

When you're working with source control on a huge team, the best way to organize things is to create branches and sub-branches that correspond to your individual feature teams, down to a high level of granularity. If your tools support it, you can even have private branches for every developer. So they can check in as often as they want, only merging up when they feel that their code is stable. Your QA department owns the "junction points" above each merge. That is, as soon as a developer merges their private branch with their team branch, QA gets to look at it and they only merge it up if it meets their quality bar.

Continua alla fonte: Using source control tools on huge projects

Print | posted on venerdì 1 dicembre 2006 08:03 |

Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET