Written by: IT Team on September 22, 2017.
A version number can stand for e.g. number of changes comparing to the older version. Here we can see that the version is 3.0 that was created on July 25 2017.
It is recommended and preferable to let version numbers present all visible changes. If they are not visible then they should be something in our code that can make our scripts in products more stable so our users do not get surprised by sudden failures in product use. It should be OK if some change also is about removing bugs because doing that gives us visible changes like "no more errors".
However, when working with updates it is important to have some available documentation which explain what was done in this version and what was done in previous versions. If we have clean and understandable documentation then we have done a great job.
Back to the to previous page
Updates and developed versions
Updates and developed versions: What is it that we can read from a new version number? A version number can stand for e.g. number of changes comparing to the older version. When programming and developing software and, or some other types of scripts we often can see information about different versions. A question about some product version can be answered in different ways. What is it that we can read from a new version number? If there is some added text description together with version number then there are probably no doubts about what is changed, removed or added. A version number can stand for e.g. number of changes comparing to the older version. Also showing the date as a part of version number is a nice method of presenting the work and time when it was done. If the version number is 3.0.25072017 then we can see that as version 3.0 that was created on July 25 2017. What kind of changes can be represented by version numbers? Well, hopefully concrete changes that we do, are what we actually treat as changes. It would not be serious if developers removed some older code from their files without replacing them with new code. There is no official way of versioning software but most developers follow the general rules that we can see in e.g this article about Version Numbers. The versioning method in our example described above is also usable.
A version number can stand for e.g. number of changes comparing to the older version. Here we can see that the version is 3.0 that was created on July 25 2017.
It is recommended and preferable to let version numbers present all visible changes. If they are not visible then they should be something in our code that can make our scripts in products more stable so our users do not get surprised by sudden failures in product use. It should be OK if some change also is about removing bugs because doing that gives us visible changes like "no more errors".
However, when working with updates it is important to have some available documentation which explain what was done in this version and what was done in previous versions. If we have clean and understandable documentation then we have done a great job.Back to the to previous page
® All Rights reserved Justfindit.se Magazine 2014.