> So, I propose the following schedule:
>
> * Friday, September 9: Rails 0.14.0; begin feature freeze
> * Friday, September 16: Rails 1.0-RC1
> * Friday, September 23: Rails 1.0-RC2
> * Friday, September 30: Rails 1.0-RC3
> * Friday, October 7: All Final Drive [1] tickets resolved; Rails 1.0-RC4
> * Friday, October 14: Rails 1.0; end feature freeze
>
> The RC releases can simply be timed snapshots of trunk. If we shoot
> for having all the FD tickets resolved by RC4, then RC4 can become 1.0
> (assuming no last-minute problems are found).
>
> Whatever''s decided should be made public on the blog and mailing
list.
>
> Thoughts?
I''m all for having good time, but we need to take at least a semi-real
stab at the huge patch list before declaring a feature freeze. In my
humble opinion, I think we should be able to deal with the RC phase
over 14 days.
Also, I''m out all of October. More or less. RC stuff can run during
that for sure, just a heads up.
--
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
http://www.basecamphq.com -- Online project management
http://www.backpackit.com -- Personal information manager
http://www.rubyonrails.com -- Web-application framework