Describe the bug
Software Update changelog is not loading for me anywhere. The loading circle just appears and loops indefinitely. Started happening maybe two weeks ago. Can't guarantee.
Screenshots
Device information:
That was it. Thanks!
On this topic, is there any way to have a bit more info of what changes on every alpha? Thanks!
only by following the forum, I only collect & summarize changes for the non-alpha versions or if there are significant changes that I want people to test.
Ok thank you. I know we are not entitled to anything and I don't want it to sound like I am, but I think it would be really really great to have a little summary of what's done in each alpha version. I encounter a lot of small issues here and there (which is normal considering the complexity of the software!) and having no idea of what has been fixed or has changed is frustrating, especially if a bug appears and we can't know if it's a possible regression or an error on our side.
Thank you for your work!
I know it would be nice, but I have tried this in the past and I really can't keep up with it. Writing a description for some super obscure thing is often more work than the implementation/fix itself (and often the next alpha changes it again). The regular alpha releases are only possible because they are basically just one click and don't involve any manual steps.
I have also noted this mutiple times so I thought to chime in because I am frustrated by this from time to time too. Andreas, why not just printing out your git commit titles or something like that? I know some commit titles might be obscure, but it’d be better than nothing. I understand you might need to possibly adapt your committing habits but as little as that would bring much value to us.
I was going to say the same, the list of git commit messages or only the merge commits from your feature branches (if you use any, I have no idea what workflow you use, maybe you don't even use git and you sync your code using Dropbox 
)
as I'm the only one working on BTT, my system for commits is pretty uncommon (and would never work in a team) - but has worked beautifully for me. However it really doesn't allow to extract anything useful for release notes.
Basically every build automatically creates a commit where the message is auto-generated based on the changed files and functions. That way I can always go back to any state, but obviously it's not usable for anything else 
However maybe one good idea, I could create a thread here that collects the alpha changes:
I've just saw the latest "Release Notes" for the alpha channel and it is exactly what we need and what I've asked previously. Thank you.
Thank you Andreas 
