I brought it up in a previous post, but making docs available for older rails milestones would be useful. PHP docs, for example, show what version of PHP a method was added in or is supported for.
Not everyone uses the latest version of rails now. Back in the old days you'd be expected to update and use the latest rails version, but rails has entered it's support days now. :) On Dec 14, 2007 1:28 AM, Pratik <[EMAIL PROTECTED]> wrote: > > +1 on the OSS book idea. I have always felt that rails api docs are > not as bad as people make it sound like. I like django style book > idea. > > I guess irc/mailing list are good enough for question/answer. There is > no point in spoon feeding. > > On Dec 14, 2007 7:07 AM, Rob Sanheim <[EMAIL PROTECTED]> wrote: > > > > Has anyone looked at what other OSS projects have done differently to > > enable successful doc projects created or contributed to by the > > community? I'm thinking in particular of the django book, and maybe > > also php.net. What do they do differently to address the people > > problems that we see in the Rails community? > > > > - Rob > > http://robsanheim.com > -- > Cheers! > - Pratik > http://m.onkey.org > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
