In our ongoing effort to enhance transparency, I’m excited to share our new Forge Roadmap with you. This roadmap is dynamically updated every hour, reflecting the latest insights from our internal Jira Product Discovery roadmap.
We want to be upfront about our approach: we may make mistakes and will adjust our plans based on feedback from both customers and developers. We understand how disruptive changes can be, which is why we are committed to transparent and early communication as the Forge Platform continues to mature.
The initiatives listed are not yet 100% exhaustive. I am working with all ecosystem teams internally to surface all the initiatives they are considering or working on this year.
We are intending to have changes to our public roadmap being shared to the Changelog as well.
We recently announced that new platform extensibility will be delivered via Forge. This doesn’t mean that we’re not supporting and developing for Connect still; for example, we’re working on App Editions and other key enablers on the Connect platform. However new extensibility (such as Rovo Modules) will only be delivered on Forge.
Thank you, this looks great! Is it accurate, based on this, to say that Forge Storage improvements are mostly paused to start work on the RDBMS service? Which sounds ok to me: a SQL database would handle most of those enhancements. It’d be helpful for us to know if it’d be better to wait a few months for some of those features or do development to hold us over until SQL is released.