Hi
Internet on
Automatically download updates yes
Update Channel : Beta
4.0a (4.10.4.6016) on machine.
Update Now reports no updates available.
Restart has no effect either (apart from restarting that is)
Set update channel to stable. I believe service releases are pushed out on the stable channel, not the beta channel for some reason. See http://wiki.logos.com/Update_Channels for more info, though I've never fully been able to understand (or agree with) the way it works.
Thanks Rosie
that seem to be hitting my download allowance nicely
That worked for me as well. Although I thought that beta pushed to stable automatically? Maybe not...
Nope, if you've intentionally set your channel to beta, you stay on beta until you change it. I think if you get a beta by downloading it directly from the server (not setting your channel to beta) then you'll stay on default, which will get you the stable releases when they come down the pipeline, but don't quote me on it. Like I said, I've never quite understood how this whole thing works. I am on beta all the time, but I don't get the SRs unless I download them explicitly. It's annoying, but I've learned to live with it. I know I could set my channel to stable and then back to beta again if I wanted to, but I'm likely to forget.
On Windows at the moment, if they released a 4.1 SR-4, it wouldn't make sense to push that to the beta channel, since the beta channel is on 4.2. The fixes in the service release end up in the beta at some point anyway.
Also, I'm pretty sure 4.1 SR-1 through 4.1 SR-3 were shipped to the Windows beta channel.
Yeah, I saw it does not. I'm going to just keep changing my update channel back and forth as new releases (whether stable or beta) come out. That way I stay up-to-date. [H]
I'm going to just keep changing my update channel back and forth as new releases (whether stable or beta) come out.
I'm concerned that many people who are using the beta channel may not quite understand the potential implications. Allow me to illustrate with an actual possible scenario that *could* have occurred earlier this year (with the Windows version):
This scenario is not only possible, it is likely. There will be moments in the path where switching is possible without much, if any, consequence (like today). But it is not a good idea to count on being able to do this at will.
Hi Devs
I was a happy Beta junky until a missive from David actually put doubts in my mind. I understood him to be saying that the Developers would not be rushing out fixes to Beta versions because there was a stable version out and users have an alternative to being in the Beta program.
I enjoy the stimulation of working with the Beta and the fellowship of the forum community but I think that I will be staying on the 'Stable' channel for a while.
On that channel I have leverage with customer services - this is the program I paid for and which I should expect to work to the standard promised.
If I move to the Beta channel I have no 'right' to demand fixes to regressions or bugs as I have stepped out voluntarily into dangerous waters.
I think that Logos needs at least an implicit agreement with its Beta crew to...
1. Prompt attention to regressions and bugs that compromise core usability eg sync problems - download problems - search performance ; .
2. That 'improvements to the stable release are incorporated into the Beta channel whenever possible at as close to the stable release as possible.
If this sort of understanding isn't available there is a huge disincentive to move to the Beta channel and a number of competent Beta testers will be lost to the Dev team.
Also the Developers need to be aware of which channel users are on when telling them that a fix is available in a particular version. I note that the main reason for many contributors upgrading to the latest stable release was the 'incredible shrinking window' bug. But that fix was not available to those on the Beta channel.
There will be moments in the path where switching is possible without much, if any, consequence (like today). But it is not a good idea to count on being able to do this at will.
For future repeats of 4.0a SR-1 situation (i.e. beta channel at same release as stable), wonder about releasing first to beta channel, then releasing to stable channel ? (possibly on same day - better than changing update channel to default - install update - change update channel to beta - much rather keep update channel set to beta)
On Wiki page http://wiki.logos.com/The_Logos_4_Beta_Program noticed 4 PC beta releases followed by stable release: 4.01.3.4533, 4.02.3.7337, 4.03.3.9511, 4.10.4.5986 (usually release candidate declared "Gold" next day). Likewise noted 4 PC stable releases ignored (skipped) for Beta: 4.01.3.5180, 4.02.3.8750, 4.03.4.0512 and 4.04.4.3415 (last stable PC service release with bug fixes - beta channel already had newer version).
Wonder about Mac Beta sub-forum ? (like PC Beta sub-forum) Existing Logos 4 Mac forum becomes stable release discussions; Mac Beta sub-forum focuses on beta discussions - lots of bug posting and replication.
Observation: PC Beta sub-forum appears on Logos 4 forum page (at bottom of page) => http://community.logos.com/forums/76.aspx
Keep Smiling [:)]
For those wanting to get off of the beta channel, this might be of interest:
http://community.logos.com/forums/t/26388.aspx
