small medium large xlarge

22 Nov 2008, 12:33
SoftMind (6 posts)


Rails 2.2 is now officially out today and this edition is yet to come out in march 2009.

That means there are still 90 days to edit Rails 2.2 missing features with more details.

Can we expect full coverage now…?


22 Nov 2008, 15:45
Dave Thomas (366 posts)

We’ve been holding back until 2.2 was released (it was still changing, even after the last RCs). Now that it’s out, Sam will be integrating it into the book.

22 Nov 2008, 23:42
Giuseppe Caruso (22 posts)

Thanks a lot Dave, you made a great work following all these releases. Your book is great. But I would like to know if this is slowing the book’s final release. Thanks again.

23 Nov 2008, 15:04
Dave Thomas (366 posts)

Sam’s working hard on upgrading the book to 2.2. We’ll release a beta once it is ready, then probably one more beta before we go to press. We’ll announce the final print date once we know it.

10 Dec 2008, 15:51
XIAOYU CHEN (5 posts)

I have 1 question and 1 suggestion:

Question: When will 2.3 come out? Is it possible to wait for a few months for 2.3.

Suggestion: Is it possible to create a life time subscription for this book.

10 Dec 2008, 17:23
Simon Starr (1 post)

That idea of lifetime subscriptions sounds great to me - is this something you’ve thought about at all?

Cheers Simon

16 Dec 2008, 02:21
Sam Ruby (633 posts)

I don’t think that anybody knows when 2.3 will come out. I seriously doubt it will be in a few months.

Dave and I have had initial discussions on subscription models, but have not come to any tangible conclusions. I will say that I’m open to the idea.

08 Jan 2009, 02:08
David W. Wormuth (7 posts)

The Rails Blog states that 2.3 will be released in January. I’d certainly like to see the book come out with a current version, not 2.2.2 if it means waiting a week or two longer.

08 Jan 2009, 03:12
Dave Thomas (366 posts)

Here’s our problem: we’ve held off in the past based on announcements. When those announcements have proven to be optimistic, folks have said “why is the book late?” And, having held off, we end up yet closer to the following announced date, and then the one after that. Keep it up, and we’d never finish. For example, if we wait a month or two for 2.3, then people will say “hold off for Rails 3”, and the 3.1, and so on and so on.

So we have to put a stake in the ground. We’ll be releasing for 2.2, but will also mention known areas where 2.3 is different. Then, going forwards, we’ll be thinking about a better way of publishing against such a rapidly moving target.


You must be logged in to comment