Beta safety question

I am very interested in running specifically the newest beta release so that I could testdrive the new systematic theology guide section, and the features that are new in the concordance tool. Do most of you guys who run beta have separate machines that are just less important to you and therefor you are willing to risk the possible problems which are warned about in the other posts?

Is this particular release relatively stable and worth me giving it a shot? I do back up my machine regularly but I definitely use this computer for work/ministry so it would be devastating if it had a major malfunction.

Any suggestions?

Find more posts tagged with

Comments

JT (alabama24)

Do most of you guys who run beta have separate machines that are just less important to you and therefor you are willing to risk the possible problems which are warned about in the other posts?

I definitely use this computer for work/ministry so it would be devastating if it had a major malfunction.

I think you will find that it varies from user to user. My advice: If you use Logos for your work and only have a single computer, don't beta test. You can minimize your risks by:

waiting until later rounds of testing (i.e. RC-1)
making sure you are in a down time at work (i.e. Friday aint a good time to download a beta if you are preparing a sermon for Sunday).

I am very interested in running specifically the newest beta release so that I could testdrive the new systematic theology guide section, and the features that are new in the concordance tool. Do most of you guys who run beta have separate machines that are just less important to you and therefor you are willing to risk the possible problems which are warned about in the other posts?

Is this particular release relatively stable and worth me giving it a shot? I do back up my machine regularly but I definitely use this computer for work/ministry so it would be devastating if it had a major malfunction.

Any suggestions?

Or test drive it in a virtual machine on your primary system using Parallels, VMware, VirtualBox, etc.

MJ. Smith

Is this particular release relatively stable and worth me giving it a shot? I do back up my machine regularly but I definitely use this computer for work/ministry so it would be devastating if it had a major malfunction.

Any suggestions?

I don't run separate machines but run under separate user accounts on one machine when there are major changes. When possible, one account is Verbum and the other Logos so that I don't forget where I am. I have never had a problem with this approach. Often, I run Logos beta and Verbum stable under the same account once we are past beta 2 - by then I know if there are dangers in that "sloppy" approach.

James Taylor

https://community.logos.com/discussion/comment/733053#Comment_733053

thanks for the tips, I will look into the options you all mentioned and see what will work best for me to join in on the next beta.

Jack Caviness

Is this particular release relatively stable and worth me giving it a shot?

Has been for me. Mac OS 10.10.3

I have a virtual machine running Windows 7 as a backup in case the unthinkable happens. I just need to launch it periodically so that it is reasonably current.

Mark Barnes

Is this particular release relatively stable and worth me giving it a shot? I do back up my machine regularly but I definitely use this computer for work/ministry so it would be devastating if it had a major malfunction.

I use the beta on my primary machine, but I know that if I get a completely disastrous bug, I can use a stable version on my wife's laptop. I wouldn't risk it otherwise.

That said, it's very rare that a bug in a beta will prevent you from using the software entirely. That hasn't happened to me since 2010.

James Taylor

https://community.logos.com/discussion/comment/733168#Comment_733168

it's very rare that a bug in a beta will prevent you from using the software entirely

Ok, I'm in. There are other users at the office, plus of course I can use mobile app, and the web app if someone crazy arises. what is the average time in between beta releases if there is destructive bug? How much down time are we talking before an issue is typically resolved?

Thanks,

James

Dave Hooton

https://community.logos.com/discussion/comment/733174#Comment_733174

what is the average time in between beta releases if there is destructive bug? How much down time are we talking before an issue is typically resolved?

Beta releases are weekly for the 6 week cycle. As you might have seen, a fix for two "destructive" crashes on Information and Power Lookup was available by Wednesday (2 days later) but more persistent bugs can ruin your Study prep for the weekend!

To avoid any impact from a "destructive" bug you should install the beta in a separate user account. You can avoid a resource download by using a safe quick installation.

JimTowler

https://community.logos.com/discussion/comment/733184#Comment_733184

I run the beta on my laptop and main desktop pc.

But I would not normally update them both at the same time, so I have options. Also I have my iPad and the browser options.

But I also don't use this for work so if I was really stuck I'd wait until it all gets sorted out.

The normal advice is to not run betas on my primary (or only) device if you depend on it and have "work" and timelines to hit.

Also, leave automatic downloads off so you only download and update when it suits you, so defer it until after your deadlines. Never patch the computer OS and update apps as a stalling tactic when you have work to complete [:$]