How do I branch and tag before and after release?

Question

I was thinking about the deployment process that I am currently using, and I am wondering if there is a good way to handle the fork / tag of the code that will / was put into production.

At some point, I want to create a branch as a release branch and make any changes to the last branch and release it. Then after freeing I want to save it as a tag.

To clarify, I am looking for conventions for naming, branch processing, and tag processing. I am also wondering if there are alternatives to the way I talk about handling the situation.

• Do you call release branches or use the same release branch with new code every time?
• Delete release branches if they exist as tags
• What do you call your branches / tags?

Answer 1

I suggest reading this answer

SVN Release Management

Basically, there is one branch called RELEASE, which you can tag from there if you want. And save the short-edged code version in the trunk

As for naming releases, it depends on what suits you best and those who see the release number.

Think about how to use MajorRelease.MinorRelease, and then maybe somewhere for those who are technically interested, you can even specify the patch release number (for example, autoupdates of the application and major.minor remains the same).

: → / : (, ) :

Answer 2

, TFS.

Answer 3

. :

 project_repository
|
| -   trunk//   .
|
| -   //   /   .
|
| -   //   .    |    | -   //        | -   daily//    .

, , :

• , (: admin_module_refactor).
• (mayor.minor.micro, : 1.0.2), release. (: YY_MM_DD).

, . .

Answer 4

CruiseControl.Net. , dll 6.5.4.1234. 6 5 , . 4 ( 1234 reset 0, ). 1234 1235.

( 6.0.0.x), Branch_6_0. 6.0.1. 6.1 7.0.

CruiseControl (dev test). , .

Answer 5

-

, . , , , . . , , , .

Do not try to make changes to the release branch, as you may lose them, or confuse time by linking them to the body.

An alternative approach to branching a release is to make all the changes to the structure of the trunk, and when you are ready, create a release / tag branch. For a small developer store, this is usually the easiest way. (Another approach works well when you make big changes to a product that everyone else makes to it as well).