1

Topic: "Internal" intermediate versions of a product, numbering

By development of a ready product which is planned to release, we inside work for ourselves with intermediate internal "versions". And it turns out that such internal version in which we conduct development of any new functionality, at us not one, and a little. For example, in one "the internal version" development of the functional unit-1 is conducted. And in another "the internal version" development of the functional unit-2, in the third - the functional unit-3 is conducted. Then these functional blocks unite and the version for testing to release turns out. If any functional block by the time of "join" had not time to complete, it continue to do in that "the internal version". As a result such situation when there are some the intermediate internal versions in which something is developed and finished was added. It creates some problems with "storage" what functional block in what intermediate version is developed and at what stage of readiness is. There was a necessity of numbering of these intermediate versions. And it turns out that is necessary "" not only the intermediate versions of a product, but also functional blocks. To trace communications in between. How it is better for making? Somebody has similar situations? How with them consult? What format of number is better for using for numbering of the intermediate versions and functional blocks?

2

Re: "Internal" intermediate versions of a product, numbering

E> somebody has similar situations? E> as with them consult? E> what format of number is better for using for numbering of the intermediate versions and functional blocks? The first 3 numbers - the trunk version we do a feature -  from a trunk and appears 4 number - version number in a feature. On the first 3 it is visible to digits, whence is went a feature-branch

3

Re: "Internal" intermediate versions of a product, numbering

K> the first 3 numbers - the version of a trunk And a trunk is that such?

4

Re: "Internal" intermediate versions of a product, numbering

Hello, es3000, you wrote: E> such situation when there are some the intermediate internal versions in which something is developed and finished As a result was added. E> it creates some problems with "storage" what functional block in what intermediate version is developed and at what stage of readiness is. E> there was a necessity of numbering of these intermediate versions. E> and it turns out that is necessary "" not only the intermediate versions of a product, but also functional blocks. E> to trace communications in between. E> as it is better for making? E> somebody has similar situations? E> as with them consult? E> what format of number is better for using for numbering of the intermediate versions and functional blocks? Not absolutely clearly what for are necessary in the presence of VCS (version control system) and issue tracker. Do branch on each functional block, and issue tracker at you the description of each functional block should be finite, and the description of that consists of what units the intermediate version. And certainly there should be integration VCS and issue tracker. In everyone commit in VCS refer to task number in issue tracker. As a result if you need to estimate a state of affairs simply come into the necessary task in issue tracker and look.

5

Re: "Internal" intermediate versions of a product, numbering

Hello, es3000, you wrote: K>> the first 3 numbers - the version of trunk E> And the trunk is that such? The main branch actually at us them a little instead of one (on major releases), but is details

6

Re: "Internal" intermediate versions of a product, numbering

Hello, es3000, you wrote: E> As it is better for making? I would make named  and that from a name  it was clear, what feature in it do.

7

Re: "Internal" intermediate versions of a product, numbering

Z> not absolutely clearly what for are necessary in the presence of VCS (version control system) and issue tracker. At us the development environment is not integrated with VCS. How in this case to use VCS?

8

Re: "Internal" intermediate versions of a product, numbering

Hello, es3000, you wrote: Z>> not absolutely clearly what for are necessary in the presence of VCS (version control system) and issue tracker. E> At us the development environment is not integrated with VCS. E> How in this case to use VCS? , in the scenario described by me integration IDE with VCS is not necessary. I IDE at all did not mention. Enough the elementary integration VCS and issue tracker. I mean that in commit message VCS write "Made that within the limits of the task #490", and after push/commit this message gets in issue tracker to the task 490 in the form of the message "branch-name/commit#1021: Made that". You do  directly from IDE or from the separate program of a role does not play. It is possible certainly not only with VCS and IDE to integrate, but any plug-in to deliver, for a dial-up #490 that at a dial-up "#"  the task list "assigned" on the given developer, but the circuit perfectly works and so without helps.