CAcert Code Development list.

[Benny Baumann <benbe AT cacert.org>]

Hi,

Am 18.01.2014 18:39, schrieb Bernhard Fröhlich:
> Hi there,
>
> I just stumbled over two cases (#1135 and #1237) where the database
> structure has been modified during installation of the bug.
That's a quite rare occation. And that there are two bugs in this short
time frame is coincidence.
> So the database was modified and left the documentation at
> https://wiki.cacert.org/Software/Database/StructureDefined outdated.
IMHO this should be noted in the ticket and left for critical to be
updated when the patch is being installed.
> 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.
Not necessary IMHO.
> Of course this new status should only be set if there is documentation
> that must be changed.
Which is, as mentioned above, quite rare.
> I'm primarily thinking of modifications of the DB structure, but there
> are, or could be in the future, other documentation like:
> - User Manual
We have a user manual? ;-)
> - (Testserver) Installation Process
Up to critical IMHO.
> - Regression Test Procedures
Which regression tests?
> - https://wiki.cacert.org/Software/UsedFunctions
Can be done once in a while as a good PHP editor provides this
information up-to-date automatically. This is only for quick reference
if no such editor is at hand.
> - Software Structure documentation (just imagine this! :))
Wait? The software has a structure? Tell me more! :P
> - ...
>
> How do you think about this?
Little benefit IMHO. Or at least you do not sound quite convincing ...
>
> Ted
> ;)
>
Regards,
BenBE.

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