@Bob_Myers wrote:
Great conversation. My two cents, expanding on some points others have made:
I get the point that developers can choose how often to upgrade. Let's say I'm on Ember 1.11 and want to wait a year to upgrade. Where do I find a consistent set of 1.11 docs for me and my devs to look at?
The deprecation strategy is cool. However, even with watson and Ember inspector, it's still underpowered. I can't see where the deprecations are in my code. I am also too stupid to figure out how to turn off the ones I don't want to see.
I can't help but feeling that there is a bit of a self-reinforcing cycle going on in the six-week release plan. The releases have more bugs than they should. It's not really quite good enough to say well, then, report them. The docs and migration guides aren't ready, as others have mentioned. Not all the features are there, so people who want some of the features have to upgrade and then upgrade again.
I don't know if there's such a thing as best practices in upgrade cycles. But I have to agree with the great majority of points made by @domchristie pointing to the notion that six weeks is too fast.