The following roadmap represents Vaadin team's current expectations of its product development schedules and future directions. This is intended for informational purposes only and should not be interpreted as a commitment. It is more likely than not that the schedules and roadmap targets change in the future. These changes are updated on this web page regularly.
Vaadin Framework maintenance
Major version 7 is supported with regular maintenance releases every 2 weeks. Major focus is on continuously increasing the quality of the framework. Covered by the bug fix priority service.
Major version 6 is covered by the bug fix priority service. In addition to prioritized bugs, only security and other major issues are addressed.
Vaadin Core Elements 1.0
- Combo box
- Date picker
Vaadin Core Elements 1.1
- Angular 2 APIs
Vaadin Designer 1.1
- Support for IntelliJ IDEA
Vaadin Plug-in for Eclipse 3.0
- Default project type change from Ivy to Maven
- Better support for Maven projects
- Project templates using existing Maven archetypes
- Notification center integration
- Angular 2 APIs
Vaadin Framework 7.7
- Maven build: Easier framework builds with Maven
- Automatic widget set configuration in Maven projects
- Bug fixes
Vaadin Framework 8.0
- Next generation data binding
Vaadin Spring 1.1
- Spring Security
- Spring navigator support
5 weeks late (31 Mar 2016 18:00:00)
6 days late (27 Apr 2016 12:00:00)
4 days late (29 Apr 2016 12:00:00)
What Happens Right Now?
Up-to-the-minute list of things that the Vaadin development team is working on is maintained on the timeline.
What Happens Next?
All of the planned future development can be viewed in the milestones on this page. Milestones with a date are mostly implemented in a timely manner. Ideas on the backlogs with no date set might never get implemented.
How To Get Feature X Implemented?
There are three ways of ensuring that your favourite feature will get implemented:
- Implement it yourself. Really! Just get the sources, compile and start implementing. It is not that hard.
- Vote for a ticket of your favourite feature (requires a Vaadin Support subscription).
- Sponsor the development of the feature.
We value all suggestions for new features and will try to accomodate as much as possible. Vaadin UserVoice also contains feature suggestions which you can vote for.
How To Get the Feature In Vaadin?
Implementing a feature for yourself is one thing, implementing and documenting it in a way everyone can enjoy it is a totally different story. For the feature to get in the main release, it must be ready for everyone and the development team must feel comfortable maintaining the feature for years.
If you have implemented a feature that you consider worthy to be integrated, please post your development as a new ticket (with patch). We try to evaluate all patches in a timely fashion and will respect your contribution and try really hard to make it happen.
All version numbers for Vaadin products are of form major.minor.maintenance.postfix. Major releases are released, when new features require breaking backwards compatibility. Minor releases are released for adding new features that maintain backwards compatibility. Maintenance releases fix bugs and contain no new features. The postfix is optional indication of stability. For more info on version numbers, read this blog post.
Each major release of Vaadin Framework is maintained for at least 5 years after the initial public stable release of the major version. A major version is maintained with minor and maintenance releases. Only the latest minor release for each major release will receive maintenance releases.
Currently supported major versions are:
- Vaadin Framework 6 (maintained until the release of Vaadin 8)
- Vaadin Framework 7 (maintained at least to the end of Feb 2018)