Re: [Beaker-devel] Beaker-project.org updated

2013-02-26 Thread Dan Callaghan
Excerpts from Nick Coghlan's message of 2013-02-27 12:06:13 +1000: > On 02/27/2013 08:32 AM, Dan Callaghan wrote: > > Excerpts from Nick Coghlan's message of 2013-02-26 19:32:55 +1000: > >> In relation to this - perhaps we should build the develop branch with > >> Sphinx in warning mode? > > > > We

Re: [Beaker-devel] Beaker-project.org updated

2013-02-26 Thread Nick Coghlan
On 02/27/2013 08:32 AM, Dan Callaghan wrote: Excerpts from Nick Coghlan's message of 2013-02-26 19:32:55 +1000: In relation to this - perhaps we should build the develop branch with Sphinx in warning mode? We could, although we then run the risk of doc errors not being noticed until we go to d

Re: [Beaker-devel] Beaker-project.org updated

2013-02-26 Thread Dan Callaghan
Excerpts from Nick Coghlan's message of 2013-02-26 19:32:55 +1000: > In relation to this - perhaps we should build the develop branch with > Sphinx in warning mode? We could, although we then run the risk of doc errors not being noticed until we go to do the release. At least now we are forced t

Re: [Beaker-devel] Beaker-project.org updated

2013-02-26 Thread Nick Coghlan
On 02/26/2013 07:31 PM, Nick Coghlan wrote: I just updated the website to bring the status of the various design proposals mostly up to date, but more importantly to bring the draft docs for 0.12 up to date, including the release notes: Design proposals: http://beaker-project.org/dev/ Draft docs

[Beaker-devel] Beaker-project.org updated

2013-02-26 Thread Nick Coghlan
I just updated the website to bring the status of the various design proposals mostly up to date, but more importantly to bring the draft docs for 0.12 up to date, including the release notes: Design proposals: http://beaker-project.org/dev/ Draft docs: http://beaker-project.org/docs-develop/ R