drafts section of the juju docs

[Gustavo Niemeyer]

On Wed, Jun 20, 2012 at 5:26 PM, Mark Mims <mark.mims at canonical.com> wrote:
> I'm asking if developers can "spec review" and subsequently develop against
> an entire branch instead of a file in the drafts folder in trunk
(...)
> - submits branch for code review
> - upon approval, merges into trunk
> - docs for this feature show up on the website

This doesn't work because documentation often precedes feature
development, and follows the review process. That's one of the reasons
why it's good to have them in separate branches. The other is that we
have two implementations running in parallel today, so arguably that
documentation is for both.


gustavo @ http://niemeyer.net