CAcert Code Development list.

[Bernhard Fröhlich <bernhard AT cacert.org>]

Hi there,

I just stumbled over two cases (#1135 and #1237) where the database 
structure has been modified during installation of the bug.

So the database was modified and left the documentation at 
https://wiki.cacert.org/Software/Database/StructureDefined outdated.

IMHO a new status "update documentation" could help to keep development 
documentation up to date. The new status would be one step before 
"solved?" and could be considered as resolved with respect to the change 
log.

Of course this new status should only be set if there is documentation 
that must be changed. I'm primarily thinking of modifications of the DB 
structure, but there are, or could be in the future, other documentation 
like:
- User Manual
- (Testserver) Installation Process
- Regression Test Procedures
- https://wiki.cacert.org/Software/UsedFunctions
- Software Structure documentation (just imagine this! :))
- ...

How do you think about this?

Ted
;)

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature