To immediately update to the current stable version enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Release Notes
Download Link
Thanks for the update.
Normally you can click on the "Installed 7.7" from the Home Page to see a dropdown with a link to the release notes.
There is no dropdown available for 7.7 (7.7.0.0015) on macOS 10.12.5 (16F73).
I found the same thing.
Also, I did not see a single thing in this release for Logos Now users.
John
I've been doing a bad job at communicating dataset updates (which are different from program updates), and for that I apologize.
But the Speech Acts and Sentence Types of the Old Testament (which I believe are only licensed to Logos Now subscribers) now include major prophets (except Ezekiel), most of the minor prophets, and 2 Samuel. (I think 2Sam is in there). The next update (two weeks) will include Ezekiel, Daniel, and the balance of the minor prophets. We have 1-2 Kings, 1-2 Chronicles, Ezra, Nehemiah, and Esther remaining after that and will continue to release in whole-book chunks every two weeks until it is complete.
For a sense of what's coming (data-wise), the OT material will be integrated into Bible Browser. We're also deriving separate datasets of Questions and Commands in the Bible. These two are long requested items and one of the reasons we undertook a more comprehensive speech act and sentence type analysis in the first place. No date/release on those items, but they're all under way.
Thanks, Rick!
A line in the release notes about this would be awesome. I can't use a feature if i don't know it's there.
Thanks, Rick! A line in the release notes about this would be awesome. I can't use a feature if i don't know it's there. John
The release notes are intended only for changes to the software. Those changes will still apply a year from now if you happen to be running that version of the software. Changes to resources (datasets) may not apply a year from now (or even two weeks from now, since resources are updated independently of the application).
As Rick implied from this line, resource updates typically get communicated via a different mechanism (forum or blog post):
Andrew,
Color me confused. I thought Rick said that the update was to a dataset. I don't consider a Dataset as a resource. It's essentially a functionality of the software, which in this case is limited to Logos Now subscribers. If a new release of the software contains updates to Datasets, I think that's worth pointing out. In this case, the addition of several books to the OT Acts and Sentences Dataset can not be shown in the 'resources updated' and in fact, this kind of update, where the scope of a dataset is significantly added to, is not pointed out in any way in the Logos software. The 'updated resources' does not show this nor does the Release Notes. This is a failing which can be easily addressed by detailing what the dataset updates are in the release notes since the resource updates have never contained any information about what the updates have changed, and in most cases that's fine since the resources remain fundamentally the same, but this is not true if the scope of a dataset is improved as in this case, and i am unaware of anyplace that this is explained or notated.
As i said, i can't make use of an expanded dataset if i don't know the dataset has been expanded. Logos should consider a method to address the communications hole which currently exists regarding datasets.
Andrew, Color me confused. I thought Rick said that the update was to a dataset. I don't consider a Dataset as a resource. It's essentially a functionality of the software, which in this case is limited to Logos Now subscribers. If a new release of the software contains updates to Datasets, I think that's worth pointing out. In this case, the addition of several books to the OT Acts and Sentences Dataset can not be shown in the 'resources updated' and in fact, this kind of update, where the scope of a dataset is significantly added to, is not pointed out in any way in the Logos software. The 'updated resources' does not show this nor does the Release Notes. This is a failing which can be easily addressed by detailing what the dataset updates are in the release notes since the resource updates have never contained any information about what the updates have changed, and in most cases that's fine since the resources remain fundamentally the same, but this is not true if the scope of a dataset is improved as in this case, and i am unaware of anyplace that this is explained or notated. As i said, i can't make use of an expanded dataset if i don't know the dataset has been expanded. Logos should consider a method to address the communications hole which currently exists regarding datasets. John
Resources include books, media collections, datasets, and other strange hybrids of books and data of different kinds. New releases of software do not contain updates to resources of any kinds, although we do try to publish resource updates synchronized with software updates so that we minimize the number of times the user is forced to download things. Actually, we tend to publish resource updates on a two week cycle vs. software updates on a six week cycle.
Updates to the Speech Acts datasets should show up in the list of updated resources on the home page as "Speech Acts of the New Testament Dataset" and "Speech Acts of the Old Testament Dataset". Updates to the Sentences dataset should show up as "Sentence Types of the New Testament Dataset" and "Sentence Types of the Old Testament Dataset".
As Rick pointed out, he would like to do a better job of communicating dataset updates.
Updates to the Speech Acts datasets should show up in the list of updated resources on the home page as "Speech Acts of the New Testament Dataset" and "Speech Acts of the Old Testament Dataset". Updates to the Sentences dataset should show up as "Sentence Types of the New Testament Dataset" and "Sentence Types of the Old Testament Dataset"
As Andrew says:
Perhaps the release notes could also include new benefits, in addition to new features and tools? While I realize that a benefit can't compare to a feature or tool, it might not hurt to publicize free books and Faithlife TV subscriptions, to help make up for the lack of L8 early access features.
We're also deriving separate datasets of Questions and Commands in the Bible. These two are long requested items and one of the reasons we undertook a more comprehensive speech act and sentence type analysis in the first place. No date/release on those items, but they're all under way.
Thanks for the update. Normally you can click on the "Installed 7.7" from the Home Page to see a dropdown with a link to the release notes. There is no dropdown available for 7.7 (7.7.0.0015) on macOS 10.12.5 (16F73).
PetahChristian,
Thanks, I'll let the team know.
Andrew you may be technically correct in what you say, but a lot of users will not understand the distinction. FL have made certain promises about Logos Now membership and they need to be seen to be keeping those promises. FL need to find a medium of communication that all users will understand and look to for this information on Logos Now updates and use that method consistently. I understand once in a while things the team at FL get busy and miss updating that communication - we are all human. Just please have one place where users can go to get the latest information on what updates have taken place in regards to Logos Now membership and use it - the average Logos Now member won't be interested in the technical distinctions and be wanting to go to multiple places to find the information - FL should be presenting the information to members in an easy to access single location.
Andrew, Color me confused. I thought Rick said that the update was to a dataset. I don't consider a Dataset as a resource. It's essentially a functionality of the software, which in this case is limited to Logos Now subscribers. If a new release of the software contains updates to Datasets, I think that's worth pointing out. In this case, the addition of several books to the OT Acts and Sentences Dataset can not be shown in the 'resources updated' and in fact, this kind of update, where the scope of a dataset is significantly added to, is not pointed out in any way in the Logos software. The 'updated resources' does not show this nor does the Release Notes. This is a failing which can be easily addressed by detailing what the dataset updates are in the release notes since the resource updates have never contained any information about what the updates have changed, and in most cases that's fine since the resources remain fundamentally the same, but this is not true if the scope of a dataset is improved as in this case, and i am unaware of anyplace that this is explained or notated. As i said, i can't make use of an expanded dataset if i don't know the dataset has been expanded. Logos should consider a method to address the communications hole which currently exists regarding datasets. John Resources include books, media collections, datasets, and other strange hybrids of books and data of different kinds. New releases of software do not contain updates to resources of any kinds, although we do try to publish resource updates synchronized with software updates so that we minimize the number of times the user is forced to download things. Actually, we tend to publish resource updates on a two week cycle vs. software updates on a six week cycle. Updates to the Speech Acts datasets should show up in the list of updated resources on the home page as "Speech Acts of the New Testament Dataset" and "Speech Acts of the Old Testament Dataset". Updates to the Sentences dataset should show up as "Sentence Types of the New Testament Dataset" and "Sentence Types of the Old Testament Dataset". As Rick pointed out, he would like to do a better job of communicating dataset updates.
Also, I did not see a single thing in this release for Logos Now users. I've been doing a bad job at communicating dataset updates (which are different from program updates), and for that I apologize.
Thanks, Rick! These updates are helpful. It reminds that there are some datasets that I have put into use more. I've also woefully neglect Bible Browser, but it's very intuitive and great for exploration.
FL have made certain promises about Logos Now membership and they need to be seen to be keeping those promises. FL need to find a medium of communication that all users will understand and look to for this information on Logos Now updates and use that method consistently. I understand once in a while things the team at FL get busy and miss updating that communication - we are all human. Just please have one place where users can go to get the latest information on what updates have taken place in regards to Logos Now membership and use it - the average Logos Now member won't be interested in the technical distinctions and be wanting to go to multiple places to find the information - FL should be presenting the information to members in an easy to access single location.
Bingo.
For some reason this update is not working for me.
The program says it's updating, but then I get a message which says, "The installation of Logos Bible Software did not succeed."
For some reason this update is not working for me. The program says it's updating, but then I get a message which says, "The installation of Logos Bible Software did not succeed."
As Rick implied from this line, resource updates typically get communicated via a different mechanism (forum or blog post): I've been doing a bad job at communicating dataset updates (which are different from program updates), and for that I apologize.
I'm not sure of the proper mechanism, but I'll try to be better about communicating these in the future. I don't think the proper spot is in the release notes, those really are commenting specifically on program (software) updates (Logos/Verbum/Noet).
Perhaps a post on resource update day (every other Monday) in the Logos Now forum would be the way to accomplish it.
Thanks for being patient with us, John (and others).
Thanks Rick we just need a clear consistent easy to acess point for communication of all Logos Now updates so members can clearly see what is happening.
As Rick implied from this line, resource updates typically get communicated via a different mechanism (forum or blog post): I've been doing a bad job at communicating dataset updates (which are different from program updates), and for that I apologize. I'm not sure of the proper mechanism, but I'll try to be better about communicating these in the future. I don't think the proper spot is in the release notes, those really are commenting specifically on program (software) updates (Logos/Verbum/Noet). Perhaps a post on resource update day (every other Monday) in the Logos Now forum would be the way to accomplish it. Thanks for being patient with us, John (and others).
Here's a post for this two-week resource release cycle: https://community.logos.com/forums/t/144823.aspx
This is helpful, Rick. Thanks.
Logging started: 2017-06-15T20:43:55Z
[Removed log entries. see https://community.logos.com/forums/t/145019.aspx ]
I suggest you re-dowload the installation files and try again. If that doesn't succeed then contact Customer Support.
EDIT: Continue this issue at https://community.logos.com/forums/t/145019.aspx
Thanks for the update. Normally you can click on the "Installed 7.7" from the Home Page to see a dropdown with a link to the release notes. There is no dropdown available for 7.7 (7.7.0.0015) on macOS 10.12.5 (16F73). PetahChristian, Thanks, I'll let the team know.
Philana (cool name, BTW), you can add me to the list of users who do have the drop down. Here are a couple of screenshots. You'll notice in the first that my title bar buttons are in color (indicating the Logos screen is active). The second screenshot is after I've clicked on the "Installed 7.7" button showing the title bar buttons are grayed out (indicating the Logos screen is no longer the active screen).
Thanks, my Dad was taking Greek at the time, and my parents loved the meaning. We do have a case open for this and we'll update this thread.
This has been fixed in 7.10.
