CODEWITHSUNDEEP
versioncompatibilityupdatesaurelia
Simone Poggi
Simone Poggi

Reputation: 1468

Aurelia version upgrade policy

One thing I'd like to know about Aurelia is if it follows a compatibility-oriented update model similar to the Ember's one; I'm citing from a recent interesting article about Ember:

All the changes made in the 1.x releases are supposed to be backwards compatible, so in theory, you can upgrade from 1.3 all the way up to 1.11 with relatively few issues.

The way they do this is to incrementally deprecate things in the framework that they plan to remove, but they will keep the features (and tests) around for the entire 1.x series or otherwise shim them with compatibility layers. So while you are encouraged to resolve these deprecations as soon as possible, you are given a very long timeframe to do so.

I didn't found anything on the subject, but I discovered that Rob Eisenberg favours Ember above React or Angular, because it shares some of his design principles.

Does anybody knows anything about this?

Upvotes: 2

Views: 101

Answers (1)

zewa666
zewa666

Reputation: 2603

Take a look at the official go live blog article

If we need to make a breaking change, Aurelia is modular enough to make that easier on us and on you. Any changes of that nature will be announced well in advance and will always be designated by a major version change in the associated library. Any removal of features will be proceeded by a deprecation period.

As such we, the Aurelia Team, do follow Semver. This even includes official plugins like the Validation, I18N. All of us have been through the pain of having to cope with extensive, undocumented or unexpected changes with other libraries/frameworks as such we are working hard to save you from that experience.

The most important aspect is the deprecation period plus transition guidelines if any features are removed.

Upvotes: 1

Related Questions