I do something similar with my own app. I have a releases page where I log all updates so subscribers can see them if they care to inspect the list.
Minor updates and edits just get listed in the log; new actual real features or large-ish changes in the software’s behavior get an email update newsletter sent to all subscribers so they’re aware of it (and it brings to their attention the fact that we’re continuously improving, making their subscription more valuable over time because the product is literally better than it was when they first subscribed)
I guess I’m just trying to say that seeing a bunch of “internal update” or “refactor” listings is no problem and is welcome information. It tells us that your team is working on infrastructure! That’s great! The monthly post on the forums can fill in the background info about what those “internal updates” were all about, as they always have done.
I am currently having unexpected results while using the ‘merged with’ operator.
Now usually I would check the Changelog to see if there was something related to this and if yes then I know to quickly send in a bug report and help resolve this issue for myself and all Bubble users quickly.
However, now I will fix my specific app with a workaround and maybe I’ll look into the issue later as I do not have time to fully test the operator in every scenario to know if it’s just my app or an actual Bubble bug
Exactly? I’d think that it’s just about writing better descriptions and we’d be okay.
Totally in the opposite direction. I do hope they’re working on something better, because taking off such a page without any plans for a better replacement would be baffling.