Skip to content

Commit

Permalink
blog(embertimes#93): add mention of codemods and ember-try
Browse files Browse the repository at this point in the history
  • Loading branch information
jayjayjpg committed Apr 12, 2019
1 parent f49cb19 commit d4cb776
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion source/2019-04-05-the-ember-times-issue-93.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,9 @@ According to the results of the latest community survey, modern Ember apps are e

Seeing that a great number of Ember apps has managed to keep up with some of the latest releases is quite striking. It shows that Ember continues to deliver on its promise of **Stability without Stagnation**. As a framework that has thrived in the fast-paced front-end ecosystem for over seven years, Ember has always promoted itself as a stable and reliable solution for developers who want to make sure that the applications they're building are not only functional, but also still easy to maintain and upgrade tomorrow.

A major contributing factor for the project's stability is the fine-tuned release process and the straightforward upgrade path. The release process has been refined several times in the past. A 6-week release cycle started with Ember 1.0 (that was more than 5 years ago!) and provided the community with beta and canary builds, as well as [feature flags for public API changes that aren't yet released](https://blog.emberjs.com/2013/09/06/new-ember-release-process.html) for every single release. A few years later, the [LTS releases](https://blog.emberjs.com/2016/02/25/announcing-embers-first-lts.html) made it even easier for developers to keep up with important updates and bug fixes while still being able to upgrade their applications smoothly in their own time.
A major contributing factor for the project's stability is [the fine-tuned release process](https://emberjs.com/releases/) which offers a straightforward upgrade path. The release process has been refined several times in the past: A 6-week release cycle started with Ember 1.0 (that was more than 5 years ago!) and provided the community with beta and canary builds, as well as [feature flags for public API changes that aren't yet released](https://blog.emberjs.com/2013/09/06/new-ember-release-process.html) for every single release. A few years later, the [LTS releases](https://blog.emberjs.com/2016/02/25/announcing-embers-first-lts.html) made it even easier for developers to keep up with important updates and bug fixes while still being able to upgrade their applications smoothly in their own time.

Additionally, community-maintained tools such as [Ember CLI Update](https://github.com/ember-cli/ember-cli-update) and a plethora of codemods support developers with their upgrades. The addon [Ember Try](https://github.com/ember-cli/ember-try) is another great way to continuously test projects against the latest Ember releases and to upgrade with confidence.

The **success of the LTS release** is also reflected in the results of the latest survey, in which the [2.18 and the 3.4 LTS release](https://emberjs.com/ember-community-survey-2019/#MS_Q401) are among the most popular versions of Ember that today's apps depend on.

Expand Down

0 comments on commit d4cb776

Please sign in to comment.