Auto upgrade to 4.0c release candidate?
Last night, 4.0b upgraded to 4.0c RC on its own. I figured it happened because the RC was promoted to golden master, but no one else reported this, so I'm wondering how this happened?
I did install 4.0b RC2 before that was deemed the GM but haven't installed any betas since if it is at all relevant.
Linden
Comments
-
Linden said:
Last night, 4.0b upgraded to 4.0c RC on its own. I figured it happened because the RC was promoted to golden master, but no one else reported this, so I'm wondering how this happened?
I did install 4.0b RC2 before that was deemed the GM but haven't installed any betas since if it is at all relevant.
My guess would be that you still had your update channel set to Beta. If you click the green question Mark "?" icon at the top right of your logos screen, then click "About Logos Bible Software" you will get a screen that has the version of Logos that is running and it will say "Update Channel: beta" if indeed that is the case. If you do not want the update channel to be set to the beta site; type "set update channel to default" in the command box.
0 -
Linden said:
Last night, 4.0b upgraded to 4.0c RC on its own. I figured it happened because the RC was promoted to golden master, but no one else reported this, so I'm wondering how this happened?
I did install 4.0b RC2 before that was deemed the GM but haven't installed any betas since if it is at all relevant.
Is it possible that you had manually set the update channel to beta some time previously, then set Automatically Download Updates to No, and declined announcements of available updates until the 4.0c RC 1 update yesterday?
0 -
Melissa Snyder said:
Is it possible that you had manually set the update channel to beta some time previously, then set Automatically Download Updates to No, and declined announcements of available updates until the 4.0c RC 1 update yesterday?
No. I never explicitly set the channel. I downloaded the 4.0b RC2 installation executable, installed it and that was it. Working late tonight, so it may be a bit before I can look up what channel I'm on.
Linden
0 -
The about dialog does not indicate that its using the beta channel. Is there a command I can enter that will report the active channel?
Linden
0 -
Linden said:
The about dialog does not indicate that its using the beta channel. Is there a command I can enter that will report the active channel?
When I type "set update channel" the drop down box will indicate the channel I am not on (e.g. it will offer the option to "set update channel to default" when I am currently set to beta. The opposite occurs when I am set to default)
If you are on the default channel it will look like this:
If you are on the beta channel it will look like this:
If you are not on the Beta channel I don't know how you ended up with 4.0c.
0 -
Linden said:
The about dialog does not indicate that its using the beta channel. Is there a command I can enter that will report the active channel?
If you set channel explicitly (to Beta or Stable) it will tell you. So I surmise it is Default, which is the stable channel for an RC or "gold". Somebody at Logos may have goofed and released 4.0c RC1 on Stable but quickly realised their mistake!?
Dave
===Windows 11 & Android 13
0 -
Fred,
Thanks for the tip. The "set update channel" dropdown doesn't show either option. It does however give me the autocomplete option of "set update channel to Default". Is there an explicit command that will report the channel I'm on?
Linden
0 -
From my experience, if you have once set the update channel to BETA then you will continue to get the beta's even if you set the update channel to DEFAULT. BETA become the DEFAULT. It appears that you have to set the update channel to STABLE to stop receiving the BETA releases.
My history from which the above is extracted: I set my machines to BETA about half way through the 4.0b beta cycle to get a new feature I really needed. Once I had it, I set the update channel to DEFAULT. However, I continued to get the BETA releases including the 4.0c beta's Now that we seem to be golden with 4.0c I will set the update channel to STABLE and see if I get the first of the 4.0d beta's.
Ye heavens, hearest thou my supplication for orderly and thoroughgoing documentation?
From my former life as a programmer, I understand that many programmers would rather be incarcerated then a single line of documentation.
0 -
Frank Fenby said:
My history from which the above is extracted: I set my machines to BETA about half way through the 4.0b beta cycle to get a new feature I really needed. Once I had it, I set the update channel to DEFAULT. However, I continued to get the BETA releases including the 4.0c beta's
This is by design. By default, a beta version will upgrade to newer beta versions.
FWIW, my preferred single line of documentation for "set update channel" would be "Do not use this feature; it is for Logos testing purposes only." [:)] (See also http://community.logos.com/forums/p/7697/60930.aspx#60930 and http://community.logos.com/forums/p/13214/102323.aspx#102323.)
0 -
Bradley,
Thanks for the quick response.
I like you single line of documentation. [:)] What led me to believe that setting to default would stop the beta, was posts like http://community.logos.com/forums/p/13214/102323.aspx#102323. But maybe I am just a poor reader.
I enjoy the beta ride, but will use it sparingly. Like when we get the splash screen removed when hyperlinking.
Thanks again for all you do!
0 -
If you're using a beta, and don't want future betas, you should set update channel to stable
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Frank Fenby said:
What led me to believe that setting to default would stop the beta, was posts like http://community.logos.com/forums/p/13214/102323.aspx#102323. But maybe I am just a poor reader.
I think that Bradley (or myself) could write how it works a dozen times and people would still be confused! It was indeed never intended for users ...
Dave
===Windows 11 & Android 13
0 -
Here is what I get when I set he update channel stable.
Is the "beta", "default", "stable" operator case sensitive?
0 -
Frank Fenby said:
Here is what I get when I set he update channel stable.
Is the "beta", "default", "stable" operator case sensitive?
It's not case sensitive that I'm aware of. You'll now not get any downloads until 4.0c releases in its final version.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
The plot thickens.
Dave Hooton said:So I surmise it is Default, which is the stable channel for an RC or "gold". Somebody at Logos may have goofed and released 4.0c RC1 on Stable but quickly realised their mistake!?
I'm learning more and more to this explanation. RC2 came out today and I did not get an update, nor did update now indicate that an update was available. I manually switched over to the beta channel, checked for an update and it downloaded immediately.
Once the update was installed, the about box indicated that it was retrieved from the beta channel. Both of these findings would seem to strongly indicate that I was on the stable channel yet got the RC1 beta. Very odd that I'd be the only one that experienced this.
Linden
0
