-
Notifications
You must be signed in to change notification settings - Fork 160
Ignite UI for Angular versioning
Ignite UI for Angular is a UI component library on top of the Angular framework. Our versioning is semi-sem-ver. What does this mean? Versioning doesn't follow the <major>.<minor>.<patch>, but instead consists of the major version of Angular the code supports, and then the version of the library against the major version of Angular it supports. So our versioning follows this pattern:
<Angular Major>.<Major>.<Minor>
Beta versions:
<Angular Major>.<Major>.<Minor>-beta.<Patch>
What this means is that breaking changes can be introduced between versions 5.2.x and 5.3.x, because 2 and 3 respectively are feature updates of Ignite UI for Angular against Angular 5.
UI Components built and tested against Angular 5.x would be versioned 5.x. Initial support for Angular 5 would be versioned 5.0.0. Minor updates and patches would increment like this
- 5.0.1
- 5.0.2
- ...
Feature updates would then be versioned like this:
- 5.1.0
- 5.2.0
- ...
NOTE: Between 5.1.0 and 5.2.0 breaking changes may be introduced. As this is a major features update of the UI component library.
What happens when Angular 6 is released? Then versioning of the first update of Ignite UI for Angular that is compatible with Angular 6 becomes 6.0.0.
Starting with 5.2.x we would introduce branch per Ignite UI for Angular major version, which means 5.2.x, 5.3.x, 6.0.x, etc.