Why the 6.0b SR-2 update for Windows users?

This morning the updated downloaded and installed. When I went to read the release notes, I saw this:

-----------------------------------------------

Logos 6.0b SR-2

Logos 6.0b SR-2 (6.0.2.0075) was released on January 27, 2015.

Bug Fixes

Macintosh

Fixed bug that caused the the resource cover images in the app to appear very narrow on Mac.*** (Thread and Thread.)

Reading Plan

Fixed bug that did not give the option to delete custom reading sessions on Mac. (Thread.)

Syntax Search Document

Fixed bug that caused the the Node Property Row Headers to appear blank when building a custom syntax query on the Mac.

-----------------------------------------------

*** I added the bold underline format for emphasis.

Question: why is this update distributed to Windows users if it only addresses problems on the Macs?

Find more posts tagged with

Comments

Dave Hooton

Because of feature parity it is important to retain the same version else Mac and Windows would need different forums.

Lee

https://community.logos.com/discussion/comment/690774#Comment_690774

Logos has done this in the past. I don't think it is necessary, or advisable. It's asking Windows users to download 99.7 MB of updates to change a version number.

Francis

https://community.logos.com/discussion/comment/690774#Comment_690774

Because of feature parity it is important to retain the same version

How is feature parity effected if there are no changes on the Windows side? Is it just the version number that is changed in Windows and if so, how much of a download does it require? Just seeking to understand...

Kevin A Lewis

https://community.logos.com/discussion/comment/690785#Comment_690785

Why can't the non update version (i.e. the windows one) be updated internally by Faithlife (with the version number) and marked to be downloaded "only" on specific user request. ?

So that would mean no needless downloads - and functional parity could still be maintained between implementations.

Shalom

Sean

This is one of the many good reasons to have automatic updates turned off. I always check the notes before downloading a SR; sometimes when Logos goes through a spree of releases I can skip 2 or 3 before one comes up that seems worthwhile to download. A large percentage of them either concern features I don't use much or are for fixing Mac bugs. (And reading these forums has convinced me to never switch; using Logos on a Mac sounds like a nightmare.)

DMB

I'm just happy that the windows version is bug-free. I'm not sure what MJ's been up to the last few weeks. Or the left part of the text entry box on 'Find' not being visable a couple of days ago. Or 2 of my search tabs disappearing when another tab was closed using the 'x'. Then there's the molassas. Even Windows has moved to molassas (I'm guessing Windows was keeping some of its routines in memory that Logos is now grabbing).

On the iOS app updates, they're always killing bugs I've never even seen.

Dave Hooton

https://community.logos.com/discussion/comment/690785#Comment_690785

Because of feature parity it is important to retain the same version

How is feature parity effected if there are no changes on the Windows side? Is it just the version number that is changed in Windows and if so, how much of a download does it require? Just seeking to understand...

Nominal feature parity isn't affected** but it is advisable to have the same version numbers to avoid confusion when communicating e.g. "do you have the latest version 6.0b SR-2" (and I still have to ask if it is Windows or Mac[:)]). So SR-2 for Windows is only a change of version number, reflecting version control changes within Faithlife. The download is the same size as normal.

** SR-2 for Mac may have a bug fix which ensures complete parity with Windows!

Donnie Hale

https://community.logos.com/discussion/comment/691064#Comment_691064

Nominal feature parity isn't affected** but it is advisable to have the same version numbers to avoid confusion when communicating

Personally, I don't expect every single change to show up in the release notes. If I were to do a diff on the SR-1 and SR-2 binaries for Windows, I suspect I'd find changes in the actual instructions at some point, not just strings representing the version number, dates, etc.

Thus, if the release notes don't mention anything of interest and you're not experiencing any issues you hope are fixed but not mentioned, don't update.

Donnie

JoshInRI

I was surprised too. I downloaded and chuckled (saying something there it goes again - that silly Logos update)