On Sun, Sep 13, 2009 at 2:39 AM, Rodrigo Rosenfeld Rosas <[email protected]> wrote:
> Docrails will eventually be outdated, since it is a separated project > and it is always behind main development. I don't really know what you mean here. docrails is a branch. The Rails Documentation Team are *not* the documenters of Rails, we are the guys that have an eye in that area of the project, just that. Sure, we do a lot of work on the API, but the Rails documentation comes from patches to master. If a patch is not properly documented it should not be accepted as if it hadn't tests. You know docrails and master are cross merged regularly, there's no way it can become outdated because docrails works directly against the Rails repo. It has its own branch to be able to offer an open policy with a little safety net and strict rules about not touching code. With the purpose of agilizing doc patches that should go the LH way and good luck otherwise. We're doing the guides as well. We commented with Pratik and Mike that code patches should patch guides, but that is not being enforced in practice. As per verisioning, docrails always documents edge, both in API an guides. If you want the docs of a release you take its snapshot (guides are included in Rails releases). The public websites only have stable and edge. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
