The Logos Beta Program
Page Contents
Development Cycle
Typically every six to seven weeks, the Faithlife Corporation releases new 64 bit software versions of Logos and Verbum with new/improved feature(s)/dataset(s)/interactive(s) and bug fixes. Before these new versions are released officially, Faithlife provides public Beta test releases for both Windows and macOS. Typically Faithlife publishes several Beta releases over a period of one to two months. Each new release will have more features (some are exclusive to Faithlife Connect and Verbum Now), be more stable, OR be faster than previous builds – that means Beta releases can be buggy: can crash (sometimes a lot), some features might not work as expected, may corrupt (or destroy) your data, or have any number of other unfortunate, unforeseen consequences. Faithlife therefore recommends that you only install Beta version(s) on a dedicated testing account (although some brave souls don’t take that advice! – knowing some bugs exist for long time). Faithlife Speaks has links to many design decisions.
Towards the end of a development cycle, Faithlife Corporation will release builds that should be stable enough for daily use – a Release Candidate (RC). If no significant bugs are found in release candidate after a short period (a few days), Faithlife will make that release available to everyone (often referred to as ‘Gold’). If bugs are found, they’ll be fixed in a newer RC, with the process continueing until no more significant bugs are found. Service Releases (SR) fix significant bugs after Gold release and complete development cycle for a Logos/Verbum desktop version.
Understanding different versions
- Alpha version: A very early test version – missing some important features, and will probably have bugs.
- Beta version: A later test version – has more features, but will still have some bugs – can include non-backward compatible changes (so syncing stuff between Beta and Stable has potential to cause issues in Stable release).
- Release Candidate (RC): A version that Logos developers hope is stable enough for daily use. Note the word ‘hope’!
- Gold Release: The final version that really does have all features stable enough for daily use – exactly the same as final Release Candidate.
- Service Release (SR): After a Gold release, some bugs need fixing for stable daily use by variety of people.
How do I join the beta program?
The beta program is available to all Logos and Verbum users. The Logos Desktop Beta forum discusses beta issues, which can include interaction with Faithlife developers. Please read and heed IMPORTANT Beta Testing Information/Warnings along with 9.2 Announcement: You’re invited: Get test licenses for new beta datasets and features!
- On PC and mac OS, to join current and future beta releases, use command set update channel to beta
Recommended Beta tester behavior
Install the Beta in another User Account on your computer and use the Set Update Channel to Beta command. You will receive all releases on the Beta channel (including Release Candidate versions) whilst your other installation remains on the Stable channel.
Typical Beta tester behavior
Use the Set Update Channel to Beta command in your current installation. It is advisable to also set Automatic Downloads to NO (in Program Settings) so that you will be notified of the download and can choose whether to accept it. This allows you to check the Beta forum for details as you might not want to install a particularly buggy/unstable version!
Once a release goes ‘Gold’ you can a) do nothing and move directly into the next beta cycle when Beta 1 is released OR b) revoke the previous command with Set Update Channel to Default and receive Service Release(s) on the stable channel.
Understanding update channels
Logos has two update channels, beta and stable. These ‘channels’ (actually RSS feeds) tell your Logos software when a new version is available. The stable channel contains details for Gold release and Service Releases only. The beta channel contains details for beta and release candidates (RC), may include service release (if no public Beta available). These tables illustrate recent versions in beta and stable channels:
| Beta channel |
35.0 Beta 1 |
35.0 Beta 2 |
35.0 Beta 3 |
35.0 Beta 4 |
35.0 Beta 5 |
35.0 RC 1 |
| Stable channel |
|
|
|
|
|
|
| Beta channel |
34.0 Beta 1 |
|
34.0 Beta 2 |
|
34.0 Beta 3 |
34.0 Beta 4 |
34.0 RC 1 |
34.0 RC 2 |
|
|
| Stable channel |
|
33.0 SR 1 |
|
33.0 SR 2 |
|
|
|
|
34.0 RC 2 |
34.1 SR 1 |
| Beta channel |
33.0 Beta 1 |
33.0 Beta 3 |
33.0 Beta 3 |
33.0 Beta 4 |
33.0 RC 1 |
33.0 RC 2 |
| Stable channel |
|
|
|
|
|
|
33.0 RC 2 |
Manually setting the update channel
- By default, Beta versions read beta channel for program updates.
- By default, all other versions read stable channel for updates. This means Release Candidates read stable channel for future updates even though they are released on the beta channel..
- You can receive Beta and RC updates with version newer than currently installed by using command set update channel to beta
- If you wish to return to default channel then use command set update channel to default
- If you wish to receive newer stable releases, then use command set update channel to stable (can use in a Beta version to skip future Beta and RC updates)
- If using Spanish as default language, use: establecer canal de actualización a ...
Finding your update channel
- On a PC, if you click help icon in top right of Logos, and choose About Logos Bible Software, you can find out which update channel you are using. On macOS, click Logos on menu bar (top left of screen), then click About Logos Bible Software to show version and update channel. If you have manually specified either the stable or beta channels, this will be stated next to version number. If you are using default channel for this particular version, then nothing will be stated.
A caveat
- Regardless of which update channel you are using Logos will only install versions of the software that have a higher version number than the one you are currently running. So if you have a beta version (say 24.0 Beta 1) and you are using the default stable channel, you will not receive a service release (say 23.2 SR-2) for the current stable version because it has a lower version number: e.g. 23.2 (23.2.35) is less than 24.0 Beta 1 (24.0.06).
Understanding build numbers
Version numbers in Logos look like this 22.0.08. The 22 just means Logos or Verbum desktop verion 22. The 22 means version 22. The “.0.” means initial major release, which is incremented for service releases (SR): e.g. 23.2 is SR-2 for version 23. The 08 means this is Logos 22.0 build number 8. Faithlife development may reset the build number for each major release (prior to Version 33, the build number was reset to 0). The initial public 22.0 Beta 1 (22.0.08) had 8 builds by the Faithlife development team. Version 23 SR-2 (23.2.35) had 35 builds.
Frequently Asked Questions
- What are the benefits of joining the beta program ? Provides you an opportunity to give feedback to Logos developers about new features, and can help speed up development, and give you some influence on how features are developed along with being able to use new feature(s) month(s) before everyone else.
- Is it safe to join the beta program ? If you rely on Logos and/or Verbum software for sermon preparation or education classes, then you should make sure you have a Stable version installed on another user account or another computer. That way if you have a non-recoverable crash, or an important feature just won’t work, you’ll still be able to teach! There is also a risk that a Beta version will corrupt your documents (such as notes, collections, favorites, shortcuts, etc.), and that this corruption could sync to your Stable version. It’s therefore wise to back up your documents (especially if you have lots of notes) before installing any Beta version.
- Can I withdraw from the beta program ? Beta bugginess is not for everyone (fixing some bugs spans several Beta releases). However, downgrading in middle of a beta development cycle is difficult; see previous question for potential corruption risk. If want to downgrade from Beta to Stable version, need to completely uninstall Beta before installing Stable. Optionally can use scan command to identify, copy, and index resources from a Beta installation.
Up To Logos Bible Software Wiki