Can Logos consider to have 3 versions "Old Stable", "New Stable" and "Beta"?

Can Logos consider to have 3 concurrent supported versions - "Old Stable", "New Stable", "Beta"?

Old Stable - Something like in Logos 3, 4 & 5 where updates are not as frequent (like once in 3 months on the first Monday please)
New Stable - The current Stable, with expectation that fixes can come soon (I remember there was once with have 3 or 4 SRs in one week (for good reasons))
Beta - for the Brave

I happened to be helping quite a number of people around me with using Logos ... most do not have a lot of time to catchup with fast and furious changes in Logos 6. I can really feel the frustration of some of these people, especially those who are not so technical, those who only use Logos a few times a week, those who travel to locations where internet is not as reliable.

These people do not come to forum here, these people do not call Logos as International Calls are still expensive. I am just trying to express their concerns ... would appreciate if you can consider this suggestion.

I know we can set to no AutoDownload ... However, if Logos can identify a Old Stable version and be conscious to have that as "Stable" in the old sense of the word ... it will give these users some added peace of mind.

Thank you!

Find more posts tagged with

Comments

George Somsel

Unless there is truly a problem with the release they have, you might encourage those you are helping to turn off updates and only do them once a month (or whenever).

Dave Hooton

Can Logos consider to have 3 concurrent supported versions - "Old Stable", "New Stable", "Beta"?

Old Stable - Something like in Logos 3, 4 & 5 where updates are not as frequent (like once in 3 months on the first Monday please)

New Stable - The current Stable, with expectation that fixes can come soon (I remember there was once with have 3 or 4 SRs in one week (for good reasons))

Beta - for the Brave

See this explanation of Supported for Faithlife's position. The closest you will get to "old stable" is a Maintenance version, which receives only "Critical" fixes/updates. Until 21 Sept that was Logos 5, but now there is no Maintenance version (and no updates if you are on Vista, OS X 10.8, or older versions).

Don Awalt

https://community.logos.com/discussion/comment/766193#Comment_766193

This is the same challenges many corporations have, where updates come online and they can't control the timing across multiple apps. The problem is easier to accomplish with just one product, say Logos v. 6 (although you could have the same issue with other programs).

What I would do is this - assume I have a group of say 6 friends/associates I am supporting with Logos. I would set their machines to auto download off, once updated to a particular version - say 6.6.

I would talk with them, and decide a mutually agreeable update time - maybe once a month, once a quarter, say on a Monday night. Maybe the time in the week is different but the same week, if the people are not geographically together. If they all work at the same church, maybe it is done at the same time.

You can then talk them through getting the latest update, at the same time being prepared to explain/show/teach what is new. You could show the videos of new features, Faithlife seems to be doing that for new features now (at least with LogosNow). You can ensure the release is "stable" - for example, since Faithlife is on 6 week update cycles, pick your time (monthly, quarterly) in say week three of the cycle - the prior release will have been out and maybe a Service Release has been done already so you can be pretty sure it won't create a problem to upgrade.

Especially if you do these updates together, you could make it part social/a fellowship opportunity too!

With this the of controlled/scheduled update process, you control timing AND frequency - and yet, people get the experience of learning about new features and not just seeing updates as a disruption. It may just energize them to learn more on their own about Logo, as you could always point them (handouts?) to areas of additional research/learning about Logos or new features (including on these forums). Or you could just print out things for them to scan/read. The point is, you could even decide to do this once a year - but you have all the tools to control the process as much as you want to.

Dave Hooton

I happened to be helping quite a number of people around me with using Logos ... most do not have a lot of time to catchup with fast and furious changes in Logos 6. I can really feel the frustration of some of these people, especially those who are not so technical, those who only use Logos a few times a week, those who travel to locations where internet is not as reliable.

It seems they may like the features of Logos 6? Do any appreciate the features of Logos Now (in Logos 6) e.g. Concordance? Because Logos 5 would be a 'stable' disappointment and the risk of not being able to sync/backup their documents (presumably the reason for reliable internet) increases greatly with Logos 5 being unsupported (even if installed on newer OS than Vista and OS X 10.8).

I think you will have to lock into an individual "no AutoDownload" strategy for Logos 6 because it is supported and reliable.