Product roadmap

Past releases

How often do we release? Since 2013, starting with version 4.0, we're on a "fast release cycle", with a new major release done about every 4 months, for about 3 major releases every year. In the 2 years from February 2013 to February 2015, we had 9 major releases, and 8 additional point releases.
Why do we release often? We think more frequent releases are better because features and bug-fixes reach users faster. They also keep us almost always ready to ship, rather than having very large work in progress which can destabilize the product and then take weeks or months to fix. In short, we think that incremental development and releases are much better for everyone! Based on our experience since early 2013 when we introduced the new release schedule, we are so far (early 2015) very happy with the change.
What do releases contain? Releases address both new features and bug-fixes. Point-releases, like 4.6.1, 4.6.2 essentially contain bug-fixes and sometimes very small features. They are done only when necessary, and only for the PE version of the product. Bigger features are for the bigger releases, like 4.5, 4.6, 4.7, and we strive to do those on a regular schedule.

How far ahead do we plan? Once we've published a major release, we do the planning for the following one. You can see the future releases listed on the open milestone page, and from there, see what has been planned for the next release. We don't plan feature or bugs to be included in releases beyond the very next release, so we can react faster to our customers needs, deciding for every release what will best serve our customers.
How do we decide what improvements to include in a release? A fair amount of the new features we develop are designed in collaboration with our customers, and sponsored by customers through a Dev Support plan. Other features are added to better serve existing and future users of the product. And last, but not least, for every release we strive to do work in each one of the development tracks outlined below.

Mobile – Better support responsive design, and the ability to run our form engine on the client to enable offline support and native apps.
Performance – While Orbeon Forms has been proven to be able to sustain a fair amount of load, we 're always striving to improve the product in that regard, including reducing memory usage, reducing load time, and improving performance on MySQL.
Architecture and maintenance – Like any project, Orbeon Forms has some technical debt. It is not possible to remove all of it at once, but, like garbage collection, we want improve the code base incrementally. In addition, we want to look to the future to use the best possible languages and frameworks. This includes: modularizing of the code, taking care of issues flagged as "maintainance", drop old frameworks and adopt new ones (get rid of YUI, use Scala.js), and do more automated testing (we have almost 800 tests, but need more).
Integration and workflow – We want to make it easier to embed forms, make it easier to use HTTP/DB services for validation, allow forms to be imported/exported with dependencies, better document standard use cases / workflows, make integration with external systems/workflows simpler, include built-in Basic workflow, and more.
Form Builder modernization – We want to push the envelope and keep improving the usability of Form Builder.

For each release we would like to:

The idea is, as some of those tasks are large, to do it incrementally when possible, so that some progress is made.

Focus:

For detailed status of issues, see the GitHub project for Orbeon Forms 2018.1.

Please remember that the following schedule is a plan, not a promise:

Focus:

Please remember that the following schedule is a plan, not a promise:

Focus:

Please remember that the following schedule is a plan, not a promise:

Last updated 7 years ago