Interpretation of - Version Control

This section covers the Meteobridge PRO, PRO2, NANO SD, Raspberry Pi and VM platforms exclusively

Moderator: Mattk

Post Reply
Mattk
Platinum Boarder
Platinum Boarder
Posts: 1387
Joined: Mon Sep 22, 2014 3:24 am

Interpretation of - Version Control

Post by Mattk »

Main Version Control options are

- Get newest on boot
- Stick to version 5.2 (being the current version today)
- Use installed version

Get newest on boot is obvious, in other words current version and current build/date
Use installed version locks the current version AND Build until one changes the option from Use installed version then Reboots

The following is assuming the version is say 5.2 Build 14524 Aug 15, 2021
But is there any difference between "Get newest on boot" and "Stick to version 5.2"? in the above context?

Obviously "Get newest on boot" and Reboot will load the most current Build (14619 as of today) within the version but "Stick to version 5.2" (for example) means what?

Stick to version 5.2 with what build? The build at the time set to sticky, or Updates the current Build (essentially same as get newest on boot) or does it imply when version 5.2 whatever build was first locked down? So is there any real difference between "Get newest on boot" and "Stick to version 5.2" within the build sequence of say Version 5.2?
User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 7854
Joined: Mon Oct 01, 2007 10:51 pm

Re: Interpretation of - Version Control

Post by admin »

As long as Meteobridge's current version is "5.2". there is no difference between "5.2". Therefore, "newest" and "5.2" is redundant until Meteobridge steps to the next version.
Post Reply