Does/should website reflect (only) latest version of Ember?


#1

I just read the “EMBER 1.7.0 AND 1.8 BETA RELEASED” blog post in which e.g. the new “NESTABLE this.route” feature is described.

This new feature is not yet documented on the Ember website:

http://emberjs.com/guides/routing/defining-your-routes/

i created a new issue on github:

https://github.com/emberjs/website/issues/1681

i wonder if the Ember website should always reflect (only) the most current version of Ember?

How should e.g. this new “NESTABLE this.route” feature be documented on the Ember website?


#2

I wonder if the Ember website should always reflect (only) the most current version of Ember?

Yes, exactly true! The guides on the website should always be reflective of the current stable version.

I created a new issue on github:

:+1: - Thanks for opening an issue on the website for this.

This new feature is not yet documented on the Ember website.

This is a somewhat tricky issue, since we cannot update the website until the stable version (1.7.0 in this case) is published. Which means there is always a point in time where the guides are slightly outdated, but our community is pretty rockin’ and generally help out with these sorts of things once it has been brought up.


#3

One thing that could be improved is a list of what versions are compatible with what versions. I am trying to use query string parameters which is not possible until Handlebars 1.3 and Ember 1.7.0 from the starter kit won’t load Handlebars 2.0 but I can’t find Handlebars 1.3 to try it. So versioned sets that actually work together would be a great thing.