Should commit history be used to convey critical information to developers?

rjzii asks:

During a meeting regarding the rollback of a third-party SDK from the latest version, it was noted that the SDK developers already announced in the commit history that the latest version should not be used.

Some developers argued that this was a bad practice and there should have been something either in the source file (i.e. ‘// Don’t upgrade SDK Version x.y.z, see ticket 1234’) or in a project level ‘README’ file. Others argued that since the commit history is part of the project documentation, it is an acceptable location for such information since we should all be reading it anyway.

Read 26 remaining paragraphs | Comments

Ars Technica » Technology Lab