We’re moving forward with our implementation of QLM and I have a few questions.
To give you a little background, we are using the subscription license model and including maintenance with the subscription (versus offering it separately). So when we set up a subscription license on the QLM server, we set the subscription expiry date and the maintenance plan expiry date to same date. When a subscription is renewed, we also extend the maintenance plan expiry date.
We are also going to use the QLM “check for update” feature.
I setup up a product definition for each of our products. So each has a Product ID and major/minor version numbers.
My questions are related to product definitions, version numbers and the “check for updates” feature:
- Do you recommend that the version numbers have just 1 decimal to separate the major and minor versions? For example 2.0 would be major version 2 and minor version 0. How are the decimals in the version number treated? Our programs currently have 3 decimals like 188.8.131.52, but we really only use the first and last numbers and I can change how we set the version numbers on our apps, if needed.
- When I issue a MINOR version update, do I just update the Latest Version tab of the existing product definition with the new version number of the minor update, the url and release notes? Or do I need to create a new product definition using the “new version of existing product” option? Your article says “…to upgrade the version of a product, you should NEVER modify the version directly. Instead, you should create a new version, leaving the old one untouched.”
- For a minor version update, if I only need to update the Latest Version info in an existing product definition, then when would I create a new product definition using the “new version of existing product” option? Only when issuing a new MAJOR version update?
- When our app checks for updates and gets the Latest Version info, will it always get the Latest Version info from the highest-version product definition where the highest version product definition was created as a “new version of an existing product”? For example, assume a user is running Product ID 1 version 3.0, and there are three product definitions on the server for Product 1: versions 3.0, 4.0 and 5.0, where 4.0 and 5.0 were created using the “new versions of an existing product” option. When our 3.0 app checks for updates, will it automatically get the Latest Version info from the 5.0 product definition.
Thanks for your answers.
Please sign in to leave a comment.