How to check new features without damaging the trunk?

Question

I create branches for each new function. Then I combine them in the trunk after sending them to the test site. This means that the trunk is unstable.

I wonder if there is a better approach.

EDIT After reading the comment, I understand that I should have indicated that this is a web application. So the website for testing each branch seems a little difficult to maintain.

Answer 1

I am using the following:

branches: not always compiled, not always stable

trunk: always compiled, not always stable

tags: always compiled, always stable

live release.

, ,

Answer 2

,

Answer 3

, , . , , , ( , ) .

. . , , . - , . . .

Answer 4

/ /

, "" ... .

Answer 5

"", , , - . , , .

- , . , , , , . , , , . Else, , , , . , , - , - .

, , .

Answer 6

? , , , ,

? ?

Answer 7

?

Otherwise, a distributed version control system such as Mercurial might be a way forward. With this, you can define new repositories for each function, as well as for testing, and click on the trunk repository.