So this is the way editions work and the way they kind of give us a clearer signal. Too regular you might say, to be constantly re-evaluating whether you need to go and take another look. Every six weeks we get a minor release and a new feature or two will have landed, and that's a pretty regular cadence. And decide whether it is the right time to upgrade.
And in the beginning of the class, when we're going around and introducing ourselves, somebody pointed out that it's kinda hard to know when we want to look at our app. We don't really have those big milestones. That everything's changed, and these are the new things that you can do. But this deprives us of the ability to trump it at those major release numbers. And increasing the complexity of getting over that threshold and making that transition. We want people to be able to get over that threshold and not worry about these new features potentially causing problems. And this is part of our commitment to stability. We never, ever introduce new features in a major release. And we dropped support for legacy browsers.
#Octane 4.0 free edition code
All we do in a major releases is we strip out old code that's been deprecated, and warning you that it's disappearing for awhile.
#Octane 4.0 free edition software
And part of the reason we have editions is unlike a lot of software you're used to consuming, Ember's major releases are really boring. So I'm not here telling you about Ember 4.0 or 5.0. > Mike North: Before we get into the code, I wanna talk a little bit about editions.
Transcript from the "Ember Octane Edition" Lesson
0 kommentar(er)
