Updates To The EmberData Lockstep Versioning Technique
Right this moment the EmberData crew is happy to announce modifications to how we handle lockstep
versioning with the broader Ember.js mission.
The first purpose of those modifications is to enhance version-to-version stability for our customers. We see this being helpful in a number of methods.
First, by releasing fewer variations that include no efficient modifications aside from the model bump, we consider customers will be capable of navigate version-by-version and LTS-by-LTS upgrades with higher stability and readability.
Second, if the one modifications are bug fixes then these fixes are utilized to the newest minor
as a substitute of turning into strung out throughout a number of minors.
Third, this could allow the mission to maneuver extra rigorously at instances when extra substantive modifications
are being made.
We hope that this new coverage will enhance the power for us to spend money on improve paths for
customers utilizing older variations by specializing in offering essentially the most sturdy launch targets we are able to.
Coverage Modifications
-
When Ember.js releases an LTS, the latest launch of EmberData can even be launched as an LTS.
-
When Ember.js releases a brand new main, EmberData can even launch a brand new main.
-
New minor releases of EmberData will coincide with Ember.js’ six-week launch cadence when EmberData releases a brand new minor.
-
These modifications don’t have an effect on how and when ember-source and ember-cli launch.
-
These modifications don’t change EmberData’s LTS assist coverage or its ember-source LTS assist coverage.
- The most recent EmberData launch will all the time assist the final two ember-source LTS releases.
Mitigating Results
-
The API Docs will proceed to operate as anticipated. It is price noting that when viewing docs for EmberData the model dropdown will solely embody variations obtainable for EmberData. Moreover, hyperlinks within the EmberData API docs to the Ember API docs will take you to the matching model variety of Ember – not essentially essentially the most just lately launched model of Ember.
-
EmberData’s README has added a compatibility desk.
-
New releases (together with patch and LTS releases) of EmberData starting at present will all the time record the vary of appropriate ember-source variations within the launch notes on the time of launch.
-
EmberData will start setting an specific peerDependency on ember-source set to all examined appropriate variations matching the vary specified within the launch notes.
- Notice: this peerDependency will at instances be a lot broader than EmberData’s official LTS assist coverage of “final 2 ember-source LTS releases”.
-
Ember CLI will ship the newest model of EmberData on the time of releases within the new app blueprint.
-
The releases overview on the web site will proceed to supply directions for putting in the newest model of Ember.js, which can embody the newest model of EmberData (see earlier bullet level). The LTS web page can be up to date to trace each the Ember.js and EmberData LTS.
Examples
- ember-source releases a brand new minor (5.4), EmberData chooses to not launch and stays at 5.3.
- ember-source releases a brand new LTS (5.4), EmberData’s newest launch is 5.3 and thus releases 5.3 as LTS.
- ember-source releases a brand new minor (5.5), EmberData chooses to launch and thus bumps from 5.3 to five.4.
- ember-source releases a brand new main (6.0), EmberData will launch 6.0.
Timeline
EmberData is starting this new coverage efficient with the present launch, and has opted to not
launch on this cycle. Thus the newest ember-source is 5.4 and newest ember-data is 5.3.
