Can anybody who has used Version Control give me an idea with respect to the release numbering, what changes should be considered as minor and what major?
Thanks, djoni
version control numbering
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The major number reflects the version of DataStage. The minor number is the number of times the component has been released/promoted. The point number is yours to do with as you wish. If the point number has been incremented, Version Control does not automatically increment the minor number.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Understood and thanks. But you have not given any idea as I asked. Anything further, please?
djoni
djoni
ray.wurlod wrote:The major number reflects the version of DataStage. The minor number is the number of times the component has been released/promoted. The point number is yours to do with as you wish. If the point ...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
lack of specific DataStage guide/standard/best practise, my company has decided to specify major if any change/maintenance needs more than 90 man-days of effort (that's the second part of the Version Control's three parts numbering scheme), and minor (the last/third part) to anything else.
djoni
djoni
ray.wurlod wrote:That's entirely your choice. It depends a lot on what you do with the product, and how you do it.
I might have a different Version Control than yours.
In the Version Control that I use (comes in my 7.1.5.A), the release/version number has three parts.
The first one (leftmost) is fixed by IBM (in my case it's 50) for all my jobs/components, I can never change.
The second (middle) is what the manual calls major. The last, minor.
We can control the major and minor.
djoni
In the Version Control that I use (comes in my 7.1.5.A), the release/version number has three parts.
The first one (leftmost) is fixed by IBM (in my case it's 50) for all my jobs/components, I can never change.
The second (middle) is what the manual calls major. The last, minor.
We can control the major and minor.
djoni
ray.wurlod wrote:The major number reflects the version of DataStage. The minor number is the number of times the component has been released/promoted. The point number is yours to do with as you wish. If the point ...
Hi,
Please see if This Post helps
Please see if This Post helps
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)