juju documentation now available

Kapil Thangavelu kapil.thangavelu at canonical.com
Tue Jan 17 15:02:48 UTC 2012

Excerpts from Gustavo Niemeyer's message of Mon Jan 16 11:13:01 -0500 2012:
> > for now i'd rather we just keep a single tree for the docs, in the interests of
> > having a single place for doc contributions and html building.  After the
> I agree, but I'm not sure about what you mean by that.
> The html building and docs should be in the same branch, but this same
> branch should not be the juju Python branch, and it should not include
> documentation for the Python code. Most of the index page today is
> taken by something that resembles package names, and the people we
> want to point the documentation at won't care about the code in
> general.

The docs branch is a sepaarate series, parallel to the top level go and python 
ones. The existing inline code documentation can be generated separately. I 
guess this is what you meant by the developer docs. I was thinking of the 
specification documentation though which i'd like to maintain within the new 
doc series (ie. implementation neutral).



More information about the Juju mailing list