Note to Bob: Bugs potentially frozen in 5.2a

Dave Hooton

For users of OS X 10.6/10.7 and Windows Vista what bugs introduced by 5.2a will remain frozen after April 8?

a massive effort was made to rewrite much of the My Library code

but it introduced a lot of bugs, some of which were deliberately left in 5.2a RC1.

What bugs not fixed, or claimed to be fixed, by 5.2a will also remain?

I think that these users deserve better consideration than these examples illustrate.

Find more posts tagged with

Comments

David Paul

I'm not panicky about this sort of thing (until I'm given clear reason to be), but as a Vista user, I hope I'm given an adequate heads-up before a landmine ends up on my hard drive...at the very least, where it's located and what will set it off.

Ryan Gano (Logos)

For users of OS X 10.6/10.7 and Windows Vista what bugs introduced by 5.2a will remain frozen after April 8?

While the platforms will no longer be actively developed for, there is no reason to fear that we will not make an effort to allow users of Windows Vista and Mac 10.6/10.7 to have an enjoyable experience with our product.

According to our public release notes we released 5.0 on Nov 1, 2012. After that date we released 4.6b and 4.6c. For the most part we can think of the 4.x – 5.x transition as a good example of the type of transition we’d like to do for 5.2x into 5.next. These versions included new features for areas such as highlighting, read aloud, prayer lists, and sermon file import. They also included numerous bug fixes for areas unrelated to these features.

The issue is not whether we will continue to support 5.2a (both with updates, and with phone support). The issue is how we can use our limited resources to give users the best experience possible as we go forward while still allowing users who cannot upgrade to a new OS to use the software they have.

Ryan

Dave Hooton

https://community.logos.com/discussion/comment/579355#Comment_579355

That's a very general answer and consequently very short on the specifics of my question...

Rosie Perera

https://community.logos.com/discussion/comment/579543#Comment_579543

I think I missed something here. When did Logos say that 5.2a would be the last release that would run on OS X 10.6/10.7 and Windows Vista?

Graham Criddle

https://community.logos.com/discussion/comment/579546#Comment_579546

Hi Rosie

I think I missed something here. When did Logos say that 5.2a would be the last release that would run on OS X 10.6/10.7 and Windows Vista?

See post from Bradley at http://community.logos.com/forums/p/80475/563263.aspx

EDIT: And the referenced blog article at https://www.logos.com/support/lifecycle

Graham

Rosie Perera

https://community.logos.com/discussion/comment/579547#Comment_579547

Thanks. I had not seen that blog article; and the post from Bradley, while I saw it, had gone in one ear (or eye) and out the other, because I have Win 7 so it didn't apply to me.

I guess the chart in the blog post tells us there will be no 5.2b, so we're going straight to 5.3 next. That's nice. Looking forward to some major new features like maybe PB syncing!! (Fingers crossed.)

Don Awalt

https://community.logos.com/discussion/comment/579550#Comment_579550

The original questions seems to be diffused by what Bradley said:

"will become the new "maintenance" version for Windows Vista, OS X 10.6 and 10.7; Logos 5.3 will require Windows 7 SP1 or OS X 10.8 or later. If you're running Logos 5.2a on Vista/10.6/10.7, your system will not be disabled; Logos 5.2a will continue to receive updates to let you read the latest resources purchased from logos.com, to keep sync working, to fix critical bugs, etc. "

Doesn't this imply to the original question,

what bugs introduced by 5.2a will remain frozen after April 8?

that 5.2a will not be frozen for bugs etc.?

Dave Hooton

https://community.logos.com/discussion/comment/579556#Comment_579556

Doesn't this imply to the original question,

what bugs introduced by 5.2a will remain frozen after April 8?

is

that 5.2a will not be frozen for bugs etc.?

You forgot the word "critical". Bradley is saying that 5.2a will not be frozen for critical bugs, and the history with v4.6 shows Bradley recommending users to update to v5 because of bug fixes (amongst other reasons). Ryan responded in the beta forum that Logos "Made a huge effort to fix crashes that were experienced during the beta cycle (54 unique crashes according to our logging)." but deliberately left at least one significant regression bug in Library. Logos made significant changes to the Library code for 5.2a and a lot of bugs were introduced, but they have only committed to fix critical bugs for users of 10.6/10.7 and Vista after April 8.

EDIT: Just to clarify. A critical bug is one that prevents the application being used as intended. Crashes are obviously critical, and a bug that prevents you from tagging or rating resources is also critical, as is one that causes the panel display to flash repeatedly or show blank rows! But it isn't critical if you can't use the Page Up/Down keys when the scroll bar is working or if a Library display shows incorrect Rank information...