stefanpenner/ember-cli — pull request #1393 by achambers (2014-07-16 13:11:55+00:00)
Title: Default assets for unknown environment to production

Just wanted to open up a discussion about which version of assets is the default when the environment is unknown.

In my workflows, I want to have to code as close to what it will look like in production as early in the build chain as possible. Ideally this would be as soon as the code has left my dev box.

Therefore it makes sense to me that if the environment config is an unknown one (ie, stage, pre-prod etc), we actually default to using the production assets.

So my questions are:

- **Was there an actual reason `development` was chose as the default?**
- **If so, what is the reasoning?**
- **If not, any reason not to change it to `production`?**

/cc @stefanpenner @xtian