Every day I generally glance over the releases/changelog for Bubble on the page bubble.io/releases,, sometimes I’ll gain a tiny insight into a rollout feature not announced here or a tweak made to the editor that wouldn’t be very noticeable to general users.
But today I’ve noticed that it now just redirects to the bubble homepage rather than the list of recent rollouts and dev changes. Anybody else seeing this?
It would be a shame to see it go…or maybe its undergoing improvements 
I came here to ask the same thing!
@fede.bubble do you know what’s up with the releases page?
Fortunately it still exists in their Bubble app, but they have a server side redirect away from it.
Hoping it’s temporary maintenance or revamp, we kind of need this page because when the time of an update aligns with a related issue we’re experiencing it means we know Bubble’s caused a problem 
I know there were some changes planned but I’l ask the team so I can share some more context here
@fede.bubble Let us know!
I check this page at least once a day 
hey all.
Essentially, the team realized that the page isn’t that helpful. As you can all see, the messages are super generic and have been for a long time.
The monthly community updates we post in the forum are the better way to keep track of how Bubble releases updates to the product.
For large feature updates I agree, but I (and I know many others) find it important because Bubble still does push breaking changes / bugs more than it’d like, and with the /releases page, when something breaks, we’re at least able to correlate that with our application rather than waste our time debugging something that we can’t control
Why wouldn’t the community being able to keep track of changes not be helpful?
Case and point: ‘Run as’ from the editor is now broken and I bet the releases page shows what broke it 
It’s just a strange move because Bubble’s made good progress towards better transparency and communication, but this moves it in the opposite direction 
They probably need to save WU 
But I agree that is was helpful for some issues
@fede.bubble The reason the team realized it wasn’t helpful is because it exposed the constant iterations/releases throughout everyday to the public/shared instance. The generic messages were awful (hopefully those were not actual commit messages), my guess is those were just the public messages and internal were more detailed.
Either way, while it wasn’t helpful to “the team”, it was helpful to us in the community who monitor our apps on a daily (not monthly) basis.
There are entire features that have only been discovered because someone on the forums noticed it on that page. Also, as others have said, it’s useful to cross-reference when something isn’t working.
Just tell them to not log “Internal development” and “Internal refactor” but to keep the rest.
Yeah I have to say, pretty disappointed this has gone, like others have mentioned, it provides helpful insights at time including the debugging of potential issues that recently arise and also that transparency layer.
ok, just to make sure we are all talking about the same thing.
You are all saying that seeing “Internal refactor” and “internal development” without any other info was still helpful?
I know there were some that were more helpful, but the majority were pretty vague like this. That’s why the team was thinking these weren’t helpful anymore. I’m assuming the other messages that were a bit more specific were the ones you found helpful here
Yeah exactly.
Since “internal refactor” literally happens every single day, no way to narrow down an issue, but sometimes there would be a very specific change and it would make it pretty obvious to relate the two. Or, rarely, a minor improvement is made that is never announced, and the only way to see it is by looking at this list. So the two options as I see it are:
OR
The ones that were ‘input adjusted’ or ‘fileupload improvement’ were good to narrow down issues
OK I just found an example of what I was referring to earlier:
FloatingGroups ‘Horizontal Alignment’ can now be centered on page - Tips - Bubble Forum
@fede.bubble instead of removing this, why to not improve labelling? Maybe add description when we click on it?
As an enterprise customer who is in control of when Bubble updates are installed on our dedicated server, I use the Releases page to catch up to speed on what’s been released and what to expect when I update.
Now I have 0% trust about installing any Bubble updates again, ever, because I don’t have an easy-to-read digest of what’s occurred since the last time I updated. That’s no good because it’s recommended not to go too long between updates to avoid conflicts. I’m not going to just update blindly, that’s kinda one of the main points of going with dedicated - I get to choose when updates occur and I’m supposed to be able to do it in an informed fashion. The Release page helped with that.
Even if it’s embarrassing to the Bubble team, seeing internal updates and then hurried rollbacks to undo the damage of something gone awry was helpful information for me. Combined with discussions on the forums and official feature announcements, I felt like they were all parts to help paint a comprehensive picture.
The main thing I don’t get is… does leaving it up really do any harm? Was anyone ever complaining about the existence of the releases page?
I don’t think I’ve seen one person complain that the release notes weren’t specific enough. It seems to be a problem that’s been imagined by the team.
We were just glad that there were release notes at all!
If it’s too much of a pain to write the release note for an update, just use AI to take the PR and turn it into a one-line summary with anything sensitive removed 
