Manual please!

[Martin.Jirsak]

@cubace

It depend on the company. On a previous work we put the documentation on source tree with the implementation. So always keept in in sync no matter what how we branched or released different versions. However this is a bit complicated for people used to work with office tools like MSWord and the document was written for engineers not for consumers. But the documentation was reviewed and accepted with the code change. But it’s not very common, most company’s dont see code and documentation as one unit and often outsource the documentation to someone that at best can run the code not totally unrelated to the release. So this gives 100% coverage, and we can define the documentation as correct. If behaviour and documentation is different it is the code that does it wrong.

Hi,

Congratulations, lucky you! Great approach, process.