Here’s where we are at the moment.
I think I may have finally gotten my head around the Ember release plans. My current understanding is that:
- A 1.0 final release of core ember is imminent, possibly as soon as September 1.
- There’s another major overhaul of Ember-data (the “jj-abrams” reboot branch), which will become the master branch sometime between now and the 35th of Octvember. In other words, who knows?
Which leaves me with the following plan:
- Once Ember 1.0 is released, I’ll start on a relatively minor revision of the book that will make sure it works with 1.0, allude to some new features, maybe talk about the Ember Inspector if I get ambitious.
- I actually don’t plan to add all that much new content, it’s already 108 pages, I doubt it will go above 130. (For reference, the Backbone book is 120, with longer code samples). I want to go through an authentication example. I may talk about components or more advanced view topics.
- Some of that is just going to wait until Ember-data gets sorted out, so I’m not rewriting the thing over and over.
- The 1.0-related release may be the one that triggers the price increase (based on length). We’ll see. But it’s coming.
Work is proceeding on this a little faster. I think I have about 30 pages of text (it’s a little hard to tell because I have a lot of blank chapters adding pages).
I like what I have, but the organization is going to need work. Right now it’s really a set of interconnected essays about project topics (already written topics include points and velocity, user stories, iteration management, the introduction, and a couple of other topics.
The current plan is to start releasing actual text around WindyCityRails, September 12th. That triggers the price increase from $15 to $20, but I’ll probably soften the blow with a promotion over WindyCityRails.
If it’s not ready then, plan B is the same thing but over Ruby DCamp two weeks later.
You can buy Trust-Driven Development.
And another thing…
Weird as it may sound, this represents me trying to clear the decks because a new project has come up. It’s not official yet, and it’ll get its own blog post when it is.