Jon (LabKey DevOps) responded: |
2018-01-10 12:52 |
Hello,
If you click on the + symbol next to the module (doing that against "Core" is best since it is literally the core module of LabKey), you will see a Build Number which indicates the specific build for the 17.3 version of LabKey you're running.
Regards,
Jon |
|
rangarita responded: |
2018-01-10 13:05 |
Hi Jony,
Thanks for such a fast response! however, I'm still trying to demonstrate that my version is 17.3, as I don' t have a way to map Build Number to LabKey version (consider it will be used for the IQ)
Thanks, |
|
|
Jon (LabKey DevOps) responded: |
2018-01-10 14:12 |
Hello,
I'm a bit confused as to why 17.30 is not an acceptable number to indicate the version.
In every section that goes over versioning within the modules, everything shows as 17.30.
Does your IQ docs require it to be listed as 17.3?
Regards,
Jon |
|
rangarita responded: |
2018-01-11 05:36 |
It's mainly because documentation refers to "17.3" and in case we are exposed to an audit process I have no evidence that "17.30" is the same than "17.3".
Regards, |
|
Jon (LabKey DevOps) responded: |
2018-01-11 11:06 |
Hello,
Although a bit of an obscure area, we do provide an explanation of this here:
https://www.labkey.org/Documentation/wiki-page.view?name=sqlScripts
Specifically, this paragraph in the Modules: SQL Scripts document:
"For the core LabKey Server modules, the version numbers correspond with the name of the release. For example, modules will show that they are are 1.10 for the 1.1 release, 1.20 for the 1.2 release, etc. This is just a convention - there is no requirement that each module be at the same version number as other modules."
So 17.30 is the same thing as 17.3 in this case. Will this be satisfactory enough for your IQ documentation needs?
Additionally, in the same Core module section that I had you expand, if you look at the VCS URL, you will also see 17.3 mentioned there as well to indicate that it is LabKey 17.3 as well.
Regards,
Jon |
|
rangarita responded: |
2018-01-11 11:12 |
Hi Jon,
I think that's good enough for me, it gives me an official explanation about LabKey's version labels and its correspondence with the current software version.
Thanks a lot for your support! |
|
Jon (LabKey DevOps) responded: |
2018-01-11 11:24 |
Glad to hear this will work for you!
Please feel free to contact us via the LabKey Support Portal for Caprion if you have any additional questions!
Regards,
Jon |
|