I had the same problem with Stacks 3.5.1 and I’m on OS 10.11.6 - so unless it’s a different bug, it’s not restricted to 10.9
The bug others on this thread were experiencing was definitely a 10.9 bug (the crash reports those folks sent made it pretty obvious, it was easy bug to duplicate, and our changes showed the duplicated bug was eliminated).
That bug has also already been fixed and released in Stacks 3.5.2 earlier today.
The bug you’re experiences is different. I would love to fix that one too. Unfortunately I don’t know anything about it yet. Are you still experiencing it? I’d love to get that crash report you mentioned!
I couldn’t find a Stacks version history on the Yourhead website
Oh my gosh. I’m so glad you brought this up. Documenting all update history is one of my very favorite things (I’m not joking – I’m just weird ) – but I so rarely get and excuse to talk about it.
We keep all the details. And they’re (mostly) automatically logged, compiled and built into nice little pages for people to browse through. It’s so nerdy awesome.
So, to answer the question, you can find the link on our site at the bottom of every page. It’s just part of the standard footer partial we use. It looks like this:
Here’s a direct link to the archive: Stacks
And, just in case you still need it, a direct link to the previous version: http://yourhead.com/appcast/RW6/Stacks3/Stacks_3.2.7_3927.zip
The archive is the one part we do by hand. I don’t archive every single version – I try to curate it a tiny bit – weed out some of the short lived versions. I usually add items to the archive about a week after things stabilize.
But that’s not all
Not only do we keep lots of old versions – but we also keep the detailed history public too. On most entries in the archive there’s a link to some release notes that were sent along with that update. Here’s a link to the latest one from today’s v3.5.2 update: Stacks Release Notes
Is that all you ask? NO WAY!
You can also click on any of the items in the detailed history – and it will go to the specific info about each bug that was fixed. So you can even look at the info about the recent Mac OS X 10.9 bug. If you click on the link next to that bug, it goes to our GitHub public bug/feature tracker where you can find all the history of that bug. (In this case, there wasn’t that much – but sometimes there is). You can even contribute your own crash reports, feature requests, or just say, “Hi”. Here’s a direct link to that latest bug: crashes on macOS 10.9 · Issue #747 · yourhead/s3 · GitHub
I don’t yet have a bug filed for your crash yet. As soon as I have some info about it – you’ll be able to follow along, watch when it gets fixed (assuming you’re a nerd for this stuff too – which, I know, you’re probably not – but just sayin’).