L/V 10 Tip of the Day #62 Tracking bug fixes
Another tip of the day (TOTD) series for Logos/Verbum 10. They will be short and often drawn from forum posts. Feel free to ask questions and/or suggest forum posts you'd like to see included. Adding comments about the behavior on mobile and web apps would be appreciated by your fellow forumites. A search for "L/V 10 Tip of the Day site:community.logos.com" on Google should bring the tips up as should this Reading List within the application.
This tip is inspired the forum posts: Print/Export is broken for Search results window of specific morphological passages - Logos Forums and *IMPORTANT* - New version numbers for Logos/Verbum software - Logos Forums
When a bug repair is available for testing, it will appear in the beta release notes at Logos Beta Release History. The normal pattern for a release is beta 1, beta 2, beta 3, beta 4, release candidate 1, release (go gold). as the releases are 1 week apart (i.e. a 6 week cycle) one can calculate when a fix will be released. One cannot see future changes, only those that have made it into beta testing.
Stable (non-beta) release notes are available at Logos Release History. Note that links to the release notes are included in the announcements Faithlife provides in the forums.
If you track the beta numbers you will see that the stable release due tomorrow (10 January 2023) is 22 rather than 10.4. That is because Faithlife is changing how version numbers are handled as described in the second forum post referred to above.
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."
Comments
-
Good to know, thanks [Y]
Current MDiv student at Trinity Theological College - Perth, Western Australia
0
