Currently, we are using the following version numbering scheme for our C # Verframech Project:
< P> "Major" change number "." Create a number within that change "We want to be able to identify that frequency number and see the number of that version in that version, seeing the number.
In the past, we did something: "major release". "Minor release" "sequence from 1.0 That build number ". For example," 4.0.648 "would mean that since 64, 648 are produced - but this information is quite useless and practical, that is why we were changed to reflect iterations
Tight version numbering, now we have a problem where a different product group wants to change its recurrence for our project. L would not make sense for example, the version number, because it is not relevant to their recurrence and numbers. For example, the last of my project build was 1.0.5.1, which indicates the building before the trend. Now this is the second project that I have to make and reconstruct my project in 3rd transition.
How should I cope with this situation? How do you do the version number in your tight project?
I do track the running of tight projects, not running software projects' if any other project after a If the late starter side project is joined then this current agile project will begin with recurrence, and there will be no misalignment.
This tight project should not be possible for a technical project outside the domain to negotiate with a project within the domain, the prime minister of this process will fail and should end in all those cases, Where a shared code is in use with the base branch, so that after completion of the project it can be patched in the trunk as a cleanup phase.
Comments
Post a Comment