RFC-131: Forge Release Tracks

Hi. I appreciate the intent behind this RFC, but I think it’s a technical solution to a communication problem. We already use feature flags. We already control when features become visible to users. If I knew the dates of Jira and Confluence’s seasonal releases, I could align my feature releases to them today. No platform changes needed. The fact that I, an active Forge app vendor, didn’t know Jira had moved to three seasonal releases until reading this RFC probably says more about the real gap than any technical solution can address. Has Confluence done the same?

As Denny says, there’s also a practical gap, since this proposal appears to assume Forge-hosted execution, and we use Forge Remote in most of our apps. This reinforces my broader point: the simpler approach is to give us the context (getSiteContext, the seasonal calendar) and let us manage our own feature visibility. This will work regardless of hosting model.

What I actually need from Atlassian to align with a seasonal cadence:

  1. share the parent product roadmap so I can plan features against it

  2. publish the seasonal calendar prominently to developers

  3. tell us and commit to which parent release that platform APIs are targeting so I can build accordingly

Right now, Atlassian’s own developer platform changes (monetisation, Forge migration, deprecations) ship continuously throughout the year and demand immediate response from vendors, regardless of any seasonal rhythm.

I’d also gently suggest that before layering release track infrastructure on top of Forge, the priority should be platform stability. I have documented Forge issues that remain unresolved. I haven’t got Enterprise customers asking for feature flag orchestration, but they are asking for confidence that Forge works. The sequencing should be:

  • fix Forge

  • improve communication with app vendors

  • then build release coordination tooling

If Atlassian wants one step that would get most of the way there: ship the proposed getSiteContext API, publish the seasonal calendar, and trust app vendors to align. We will, if we know when.