Today the Ember project is releasing version 3.11 of Ember.js, Ember Data, and Ember CLI. This release kicks off the 3.12 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The ember-try addon is a great way to continuously test your projects against the latest Ember releases.
You can read more about our general release process here:

Ember in 2018 (and 2019) has been more exciting than ever! We've been working diligently to advance the project based on our 2018 Roadmap, but while we work to finish that, it is time to think about the future.
The Ember team would like you to write a blog post to propose goals and direction for Ember for the next year. The content of these posts will help us to draft our next Roadmap RFC.

Ember's conventions for project layout and file naming are central to the
developer experience. It's crucial that we get both the technical and
ergonomic details right. I wanted to provide an update about Module
Unification and our plans for the file structure in Ember Octane.
In short, we do not plan to ship Module Unification in Octane. Instead,
Octane will ship with today's file system layout, with one change: support
for nested components in invocation syntax

(This post was originally published on www.pzuraq.com)
Hello again, and welcome back! This is the third entry in the multipart Coming Soon in Ember Octane series, where we're previewing some of the various features that are landing in Ember's upcoming Octane edition, including: