Should you use branches in subversive activities if only one person is working on a project?

Question

I'm just starting to use Subversion in a C # project. I am working on this project alone, but I am trying to heal as if I were working in a group for my own training.

As I understand it, a typical way to work with subversion is to have a trunk folder that will always build. Major changes are then created in new branches, which are then merged back into the trunk when they are completed. Thus, there can be many simultaneous branches on which different team members work.

But if I work on my own, is there any point in making a branch? Say I'm at revision 100 in HEAD. I will create a branch in edition 101, and then continue working on the branch to version 110. Now I can merge 110 back into the trunk, but there is no one else in the project, so no changes to the trunk to merge again. I would just merge back to version 100, where I created the original branch.

Answer 1

Affiliates have nothing to do with how many people are working on a project. An affiliate is designed for an alternative development flow, such as various feature sets, hardware targets, or clients.

100 , . , .

Answer 2

, , , , - . .

Answer 3

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

Answer 4

, , , - , .

, , - , , , .

, , ... .

Answer 5

I hold 2 branches: development and the trunk, because you never know when you need to quickly fix the situation. I can work on new features for 1-3 weeks before moving them to production. At the same time, I may have to post corrections for production. By keeping 2 branches, I can easily install bug fixes.