Beta.0, Shipped (September 14th 2016)
The initial release of Kendo UI for Angular 2 laid the foundation of and articulated our vision for the product. We shipped 15 essential UI components, built from the ground up for Angular 2 on the same date that the Angular 2 team announced Angular 2 was final.
The release included many of the essentials necessary for building a modern line-of-business UI:
Blog post: Announcing Kendo UI for Angular 2 (R3 2016)
RC.0, shipped (January 18th 2017)
The RC release aims to be production-ready, which means that we don’t plan to ship major breaking changes of the public API afterwards. Just like Angular 2, the component packages will follow the semantic versioning specification.
Our biggest priority with this release was full coverage of the framework features:
In addition to that, we shipped four new components:editing and grouping.
In the period Jan-May, we are going to ship one or more additional RC releases, which will include the things that did not make it in RC.0—the Date Input, Calendar, and Toolbar components. New features of the existing components will be released as soon as they are ready.
Final Release, Planned (May 2017)
The final Kendo UI for Angular 2 release should iron out any outstanding problems or missing features of the included components. We are going to focus on the Grid must-haves and the form components. We are going to follow the Angular release schedule closely and allocate effort to staying up-to-date with the framework development. A few new additional components (ListBox, Menu and ContextMenu) are in the pipeline.
2017 R3 and Beyond
Once the essential building blocks are in place, we are going to explore the needs of complex business application components, like the Scheduler, TreeView, TreeList, and Editor. Our long term goal is feature parity with the current jQuery suite while keeping up-to-date with the Angular 2 framework development.
We remain committed to providing an unmatched UI suite for Angular 2. The kind that you would expect from Kendo UI.
We operate in a dynamic environment, and things are subject to change. The information provided is intended to outline the general product direction. It is intended for informational purposes only and should not be relied upon when making any purchasing decision. We may decide to add new components at any time depending on our capability to deliver products meeting Progress quality standards. The development, releases and timing of any features or functionality described for Progress products remains at the sole discretion of Progress. The roadmap does not represent a commitment, obligation or promise to deliver any products to the customer at any time.