Aurelia 版本升级策略
Aurelia version upgrade policy
关于 Aurelia，我想知道的一件事是它是否遵循类似于 Ember 的面向兼容性的更新模型；我引用 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.
我没有找到关于这个主题的任何东西，但我发现 Rob Eisenberg 更喜欢 Ember 而不是 React 或 Angular，因为它分享了他的一些设计原则。
有人知道这件事吗？
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.
因此，我们 Aurelia 团队确实遵循 Semver。这甚至包括官方插件，如 Validation、I18N。我们所有人都经历过不得不应对其他 libraries/frameworks 广泛的、未记录的或意外的变化的痛苦，因此我们正在努力使您摆脱这种经历。
最重要的方面是弃用期以及移除任何功能时的过渡指南。
关于 Aurelia，我想知道的一件事是它是否遵循类似于 Ember 的面向兼容性的更新模型；我引用 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.
我没有找到关于这个主题的任何东西，但我发现 Rob Eisenberg 更喜欢 Ember 而不是 React 或 Angular，因为它分享了他的一些设计原则。
有人知道这件事吗？
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.
因此，我们 Aurelia 团队确实遵循 Semver。这甚至包括官方插件，如 Validation、I18N。我们所有人都经历过不得不应对其他 libraries/frameworks 广泛的、未记录的或意外的变化的痛苦，因此我们正在努力使您摆脱这种经历。
最重要的方面是弃用期以及移除任何功能时的过渡指南。