6.0b Release Candidate 1 (6.0.2.0039) now available
6.0b Release Candidate 1 (6.0.2.0039) is available for testing.
Users who are running Logos 6 can update to RC 1 automatically by entering the set update channel to beta command. Users running 5.2b cannot update to the 6.0b Beta at this time.
Note that switching to RC 1 via set update channel to beta will require users to manually set the update channel back to stable once the RC becomes the stable version. In the past, we could provide a download link for the RC which would circumvent this requirement, but until the Logos 6 engine becomes freely available in February this additional step is required.
Note: 6.0b RC 1 is still beta software, and users should be fully aware of all risks associated with beta software before switching update channels. If no major issues are discovered with the RC, it will go Gold and become the next stable version.
Comments
-
Where is that setting and how do you do that?
0 -
Hi Eric - and welcome to the forums
Eric baca said:Where is that setting and how do you do that?
You type it into the command box at the top of the Logos window
Graham
0 -
Ive been getting this error when logos starts when i try openinging it. Logos has a update to install, but then i get a windows 45 error connecting to network or something like that. Maybe this will fix it.
0 -
Here is the error message i am getting.
logo bible software setup via installation of the microsoft .net framework 4.5 did not succeed
0 -
Eric baca said:
Maybe this will fix it.
I wouldn't move to the RC just to see if it fixes this type of problem.
The RC is expected to be "stable" but there may still be some issues in it
I would create a new thread and explain clearly the issues you are seeing
0 -
Thank you, i willl try and delete these threads.
0 -
Eric baca said:
Ive been getting this error when logos starts when i try openinging it. Logos has a update to install, but then i get a windows 45 error connecting to network or something like that. Maybe this will fix it.
You are getting a Windows error which must be fixed in Windows. You will continued to get the error until you successfully install the correct version of Windows .net. I don't have enough information to twll you what is needed but what I would do is:
(a) check permissions to make sure I have logged in under a user with permission to make the update
(b) check the error message on the Microsoft site to discover the most common causes of the error
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
The wiki is not clear, can you go to the beta channel to run RC and return to non beta when it goes GOLD?
0 -
Mike McKnelly said:
The wiki is not clear, can you go to the beta channel to run RC and return to non beta when it goes GOLD?
Yes - you can use "set update channel to stable"
0 -
you dont have to reinstall the software?
0 -
Eric baca said:
Where is that setting and how do you do that?
Hi Eric, this release is still technically a beta release and it's not recommended that you update just yet until it "goes gold" (ships), in which case you'll get the update automatically if you have "Automatically Download Updates" set to Yes in your program settings. A Release Candidate has the potential to become the gold release if no showstopping bugs are found in it within the first day or so, but there are no guarantees, so you won't automatically get that until it gets the green light. If you're not familiar with how the beta testing program runs, I would not use the "set update channel to beta" command. There are big warnings about using beta releases here in this sticky post at the top of the beta forum.
Dylan, posts announcing release candidates should still link to the beta warning post, because newbies unaware of how the beta program works and the risks of using beta software should not ever be encouraged to use the "set update channel to beta" command.
0 -
Dylan used to post links to the RC. Ive had great success with these.
0 -
Mike McKnelly said:
you dont have to reinstall the software?
You do if you want to go from a beta release back to an earlier stable release, but not if you switch to the stable channel after a "Gold" release
0 -
Rosie Perera said:
Dylan, posts announcing release candidates should still link to the beta warning post, because newbies unaware of how the beta program works and the risks of using beta software should not ever be encouraged to use the "set update channel to beta" command.
You're right, and I'll add that to the other post, but I didn't add it to this one since we're in the Beta forum...
0 -
Dylan Rondeau said:Rosie Perera said:
Dylan, posts announcing release candidates should still link to the beta warning post, because newbies unaware of how the beta program works and the risks of using beta software should not ever be encouraged to use the "set update channel to beta" command.
You're right, and I'll add that to the other post, but I didn't add it to this one since we're in the Beta forum...
Yeah, but the beta forum is readable by all, and a newbie (only 6 posts) stumbled on your post and seemed confused about it, so might as well add the caveat link to posts in the beta forum too, just in case. When people read the "Recent Topics" sometimes it's easy to overlook what forum the posts come from.
0 -
Rosie Perera said:
Yeah, but the beta forum is readable by all, and a newbie (only 6 posts) stumbled on your post and seemed confused about it, so might as well add the caveat link to posts in the beta forum too, just in case. When people read the "Recent Topics" sometimes it's easy to overlook what forum the posts come from.
That's fair. More precautionary information can't hurt, I suppose. Thanks, Rosie.
0
