Hey guys, I''ve just got back from a blissful two week holiday in the south island of New Zealand[1], and I''m wondering where we are with the road to 1.0. The Ajax stuff is looking nice, and I see from the timeline that there are some other cool new features in the pipeline. I think it''s important to get 1.0 out the door, and to do that I think there are a number of questions we need to think about around our release strategy for 1.0? * What date are we targeting? Our old target was this month, given that development is still in full swing I guess we''re pushing it out a bit. * When are we implementing a feature freeze? * When will we branch for 1.0? * How many betas and release candidates do we want to have? * What features are we willing to push out to post 1.0, what is a *must have*? While some of these are bound to start some heated discussions, I think it''s important to consider them as a 1.0 release is a great way to attract new developers. We can promise (and deliver) a stable feature set and push all the fun stuff into 1.x releases. Anyone have any thoughts? Anyways, I''m off to start playing with the ajax stuff. -- Cheers Koz [1] I can recommend it, though I''m a kiwi, so consider the bias.
> * What date are we targeting? Our old target was this month, given > that development is still in full swing I guess we''re pushing it out a > bit.The emergence of Ajax and a few other key features (such as eager loading for associations) has taken precedence in my focus and pushed 1.0 out a little further. As it is now, I think the prioritization for v1.0 is something like: * Wrap up Ajax nicely (there a number of key patches that I want to examine closer) * Finish eager loading for associations (this is fairly small thing) * Clear out the tickets marked for v1.0 (http://dev.rubyonrails.com/report/9 -- may need examination of the latest tickets) * Performance! This is the biggest item on the map that hasn''t yet been approached that much (besides the good work of http://dev.rubyonrails.com/ticket/912).> * When are we implementing a feature freeze?When the four points of above has been addressed. I don''t mind taking in new minor features as long as we''re still progressing on the critical items.> * When will we branch for 1.0?I''d hope that we''d be capable of reaching resolution on the points mentioned above within another month. So a branch around 7th of May with a target release of 15th of May would be nice.> * How many betas and release candidates do we want to have?I''m thinking about running for 7-10 days on a branch where only documentation patches and bug fixes go in.> * What features are we willing to push out to post 1.0, what is a > *must have*?Packaging was originally on the cards for 1.0, but no champion has been found, so that looks like it''ll be post 1.0. So will the adoption of multiple inheritance strategies.> While some of these are bound to start some heated discussions, I > think it''s important to consider them as a 1.0 release is a great way > to attract new developers. We can promise (and deliver) a stable > feature set and push all the fun stuff into 1.x releases.Definitely. Getting 1.0 out is important for a number of reasons and we should aim for it to happen soon. So what can you do (as in all)? If you''re fairly deep into how the internals of Rails work, we still need a strong champion to push performance. The work involves setting up a test application that can then be profiled and benchmarked to reveal bottlenecks in frequent Rails usage. If you want to start on something smaller, the Road to 1.0 list of tickets contains many things small and large. If you''re not sure how to approach the solution with a concrete patch, we need to get a lot of the stuff written up with unit tests demonstrating the failures. Everyone can help with that. -- David Heinemeier Hansson, http://www.basecamphq.com/ -- Web-based Project Management http://www.rubyonrails.org/ -- Web-application framework for Ruby http://www.loudthinking.com/ -- Broadcasting Brain
On Apr 9, 2005 9:01 AM, David Heinemeier Hansson <david-OiTZALl8rpK0mm7Ywyx6yg@public.gmane.org> wrote:> > * What features are we willing to push out to post 1.0, what is a > > *must have*? > > Packaging was originally on the cards for 1.0, but no champion has been > found, so that looks like it''ll be post 1.0. So will the adoption of > multiple inheritance strategies.If you don''t mind, could you point me to a link talking about "packaging". I''m not quite sure what you mean when you use that term. -Thanks Shalev