documentation audit needed

[Robert Collins]

   - Select some user stories and make sure someone could work out how
     to do them from the manual
   - Audit that all non-hidden commands are discussed in the manual
   - Make a dump (e.g. to html or text) of all online help and review/audit

[Martin Pool (mbp)]

Ianc has been doing some work on this and identified some fixes and some things needing more work. Should he close this when everything's been done?

[Vincent Ladeuil (vila)]

I don't think 'Ian Chiew' was the right assignee. Feel free to correct me.

[Martin Pool (mbp)]

> I don't think 'Ian Chiew' was the right assignee. Feel free to correct
> me.

You're right.

--
Martin

[Ian Clatworthy (ian-clatworthy)]

I've made a heap of progress on doc in 0.90. The User Guide needs some attention still before 1.0 but the rest is now in pretty reasonable shape I think.

[Vincent Ladeuil (vila)]

Shouldn't we close that bug and open some more specific ones ?

[Matthew Revell (matthew.revell)]

I'll be spending a good chunk of the last week of September and much of October working on Bazaar documentation.

On Monday I'm going to email the bazaar mailing list with my proposed plan of work to get the docs in shape for 1.0's release.

[Robert Collins (lifeless)]

Going by our bug guidelines we should not have done the last two releases - critical is 'block a release'. This really is high at most; and unless someone is volunteering to do a significant amount of writing in the next couple of weeks it won't be done for the next release.

[Martin Pool (mbp)]

I agree with Ian that this can be closed, although we still have more documentation work for the future.