Official Release Downloaded???
Just downloaded a program update and checked the about Logos tag to see what version it was up to and all it says is 4.0, no beta or anything else... Is this the official 1st release?
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
Comments
-
I think it's RC1 (release candidate 1)
MacBook Pro (2019), ThinkPad E540
0 -
Yeah I saw something posted about RC1, just was odd to not have it labeled as such in the "about" section...
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I'm not getting the update for some reason. So consider yourself lucky.
MacBook Pro (2019), ThinkPad E540
0 -
Todd have you tried the update now command in the command bar? That is how I got the update.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
No I've just been waiting for the automatic update. I thought it checked every time it started up.
It shows up here:
https://clientservices.logos.com/update/v1/feed/logos4/beta.xml
and that has always come down automatically in the past.
MacBook Pro (2019), ThinkPad E540
0 -
Frank Sauer said:
Todd have you tried the update now command in the command bar? That is how I got the update.
Yup, I got mine too...I typed "update now" in the command bar.
Thanks for this info!
0 -
No problem Robin.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Todd Phillips said:
No I've just been waiting for the automatic update. I thought it checked every time it started up.
Beta 8 and earlier checked on every startup. Beta 9 (and RC1, which is the current release) check just once per day, which is the intended strategy for the release version (to spread out the load on the servers when an update is released once the product has shipped).
If you hear that there is a new version, you can always run "update now" (as mentioned by other posters) to force a check for updates.
0 -
Bradley Grainger said:
Beta 9 (and RC1, which is the current release) check just once per day, which is the intended strategy for the release version (to spread out the load on the servers when an update is released once the product has shipped).
Makes sense.
0 -
Sounds like my WIndows 7 is set to arrive today, but I'm going to hang on until we get out of RC's into the gold release (provided you don't make me wait too long).
Sarcasm is my love language. Obviously I love you. 0 -
Frank Sauer said:
odd to not have it labeled as such
Hi Frank,
Actually it is not odd. Eventually the last RCn becomes the released version. Software companies do not create a new build, they just remove the release candidate status from documentation external to the program, the build itself does not change at that point.
Why do they do this? To avoid introducing new bugs. All changes are potentially dangerous and even changing the build number and removing the RC label would require a round of testing. Which would leave them exactly were they are today, with an unlabeled release candidate candidate.
If RC1 turned out to be bug free enough (no non-trivial software is completely bug free) it would become the gold build that would go to manufacturing. Usually RC1 does not make the grade, but it potentially could, otherwise the company would have left it as a beta.
Regards,
Clinton
0
