Iván Arroyo
@iarroyoescobar.bsky.social
Dad of twins. 🍼🍼
Web developer 💻
It is a joy to build web apps using #EmberJS
Web developer 💻
It is a joy to build web apps using #EmberJS
Reposted by Iván Arroyo
Ember's major version release strategy is super-simple:
1. Before removing a feature in a major version, it lands as a deprecation in the *previous* major. A deprecation is only enabled by default once we have a clearly documented migration strategy that covers the use-cases of the old feature.
1. Before removing a feature in a major version, it lands as a deprecation in the *previous* major. A deprecation is only enabled by default once we have a clearly documented migration strategy that covers the use-cases of the old feature.
#emberjs has released version 6.0 🎉
Nothing new, yet landed so many features.
Read more about ember's fantastic release strategy: blog.emberjs.com/ember-6-0-re...
Nothing new, yet landed so many features.
Read more about ember's fantastic release strategy: blog.emberjs.com/ember-6-0-re...
Ember 6.0 Released
Ember 6.0 continues the commitment to stability and reliability that developers have come to expect from the Ember ecosystem and further moves us towards the Polaris Edition of Ember. Get up-to-...
blog.emberjs.com
January 19, 2025 at 1:43 AM
Ember's major version release strategy is super-simple:
1. Before removing a feature in a major version, it lands as a deprecation in the *previous* major. A deprecation is only enabled by default once we have a clearly documented migration strategy that covers the use-cases of the old feature.
1. Before removing a feature in a major version, it lands as a deprecation in the *previous* major. A deprecation is only enabled by default once we have a clearly documented migration strategy that covers the use-cases of the old feature.