Questions about branching tasks

Question

I am considering moving from HG to Plastic SCM ( http://www.plasticscm.com , mainly because it seems to offer much better VS integration), and they contribute to “task-driven branching,” that is, branching from trunk for each function. This makes sense, but I had a few questions:

• They recommend not combining their tasks with the main line after they are completed. It seems very unintuitive, I would think that after testing you would want to immediately pour it back to the tip, so that later you did not need to reinstall it. Not to mention the fact that if the tasks are not merged back, and they say that the new release is suitable, you need to combine, perhaps, hundreds of different branches and make sure that they all work well together for a short period of time (testing in independence means that they will play well with others, IMHO). So it looks like he is failing, right? Do you practice this method?
• Let's say I'm wrong about the above, given the following scenario: Task A, B, C. Where B, C depend on the completion of A, it would be better to complete A, combine it back to the highway, and then work from there to B / C or under the branches of your initial branch (the branch that you created for A). Is it possible? Recommended? It seems to me a little cleaner in my head if the same person implements A, B, C. If not, it is obvious that merging back into the trunk makes the most sense.

Let me know what you guys think!

Thank.

Answer 1

, , jgifford25 answer , Subversion " , , - , , . , , , . , , SCM - , " " , ​​ SCM.

? " ". : " ". . , :

• ,
• trunk

, , . ( , ), , , - . , , - , ( , , , - ).

, , , . - , . , , - ? , .

, , . , , , . , - , , , , . " " - .

, Ubuntu . , :

, , : . , , Plastic, .

, , , , : , ( , ), .

, : . . .

PS , , . , .

PPS CI, (, , ), -, DVCS, : , , script, , , , , . ( QA ..) , , . , .

Answer 2

PR , , // (. № 4). . , , , , .

Subversion, , , . . .

- . , . , ; , . , , .

, , № 1 . №2, . , B C A? , A , B C. , , A, B C, , , . , , .