How to protect the trunk from developers

Question

We use TFS for our code: trunks + branches for coding operations. My team has 6 developers.

Problem: sometimes developers do not want to create a new branch (or use the old one) to fix / develop something. They just do it in the trunk. Well, in some cases this is acceptable. But most of the time he creates a lot of trouble.

How can I protect chests and force developers to create new or reuse old branches?

UPD . I do not want to provide read-only access to developers on the trunk (they should be able to create branches and merge them yourself). I want a compromise - I can create branches / merge, but I can not develop in the trunk.

Answer 1

Working with the body directly is almost always incorrect. Yes, this may be the most efficient way, but the interrupt process is a breakdown process that will eventually bite you.

I think this problem is best solved with the help of education, but limiting access to chests for senior developers can also help - if they are also not "infected" :)

Wortyh, , - (read: not VSS) , . , " ".

Answer 2

.

- . , , , .

. http://msdn.microsoft.com/en-us/library/ms252587.aspx

Answer 3

, @annakata. , , - SCM , , , - . , ( , ) .

, :

• . , . .

• TFS2010, . .

• , . , - . SCM , . , .

• ( ). , /, , , , , , - . .

Answer 4

TFS hook, subversion?

-, , , , , ..

, .

Answer 5

"" TRUNK? , TRUNK, ...

, , , DEV.

, TRUNK HOTFIX. , .

, HOTFIX: , , QA, , , DEV, , QA, , , , , , , , . HOTFIX, TRUNK "Branch" HOTFIX - . HOTFIX, HOTFIX. HOTFIX : A. TRUNK B. . , DEV, .

Answer 6

You can create a user group in TFS to enable read only or no access at all. If you right-click on a team project and select group membership, add these groups to the folder structure in the source explorer.