- Rolling Releases: https://developer.atlassian.com/platform/forge/rolling-releases/
Sent a request to join EAP on 17th April; nobody has responded to the request: FRGEAP-1801
- Object Store: https://developer.atlassian.com/platform/forge/storage-reference/object-store/
I was able to join the EAP but Atlassian stopped responding to feedbacks since last year, see here: https://community.developer.atlassian.com/t/bugs-and-issues-object-store-eap/88338/4
Also, are EAPs supposed to take so long? This EAP was started over a year ago in Jan. 2025.
Hello, apologies for the delay in signing you up for the Rolling Releases EAP. You have been added now.
Hi Dean,
Thank you for adding me to EAP. However, I still do not have access to the mentioned Slack channel. Could you please look into it?
Rolling Releases fyi is not an optional addon. They’re positioning that way because they’re unwilling to admit how fundamentally broken versioning and updates are in Forge.
Genuinely abhorrent that revenue penalties are in effect and migration deadlines are set while this is still in EAP.
Nor will this be a fix to the core problem: admins do not manually update apps.
Ok, we got into Rolling Releases EAP.
I think this is going to solve a ton of issues in app versioning. Credit where credit is due, this is the right direction.
Though I totally agree this should have been done before forcing migration to Forge.
I would very much also like to know the status of the Object Store EAP. It looks like it will unlock a few use cases for us, but there has been no word on when preview might be happening etc.
In PDM Slack, I was told that they are targeting moving Object Store to preview in May.
@DeanPeach when is Rolling Releases going GA?
The faceless bureaucrats have decided to plaster Connect apps with warning messages in September 2026.
I don’t want to migrate before Rolling Releases is GA given how it is literally a fundamental change to how apps are versioned, and without it your apps are far more likely to enter zombification death spirals.