----- Forwarded message from Jeffrey Walton <[email protected]> -----
Maybe the GNU Coding Standards should (1) tell a maintainer to build a release candidate before a release, and (2) make an announcement on platform-testers . Currently neither platform-testers nor release candidates are discussed in the manual. [1] This particular [testing] problem is not limited to [one project]. Other projects do the same, and they also find they have problems after a release. In the post-mortem analysis, this is a procedural problem in the release process. The release process has gaps and needs a control to contain the risk. In this case I think the control to place is: document release candidate testing in the manual. That puts everyone on the same page and ensures some coverage to catch some of these problems. Jeff ----- End forwarded message -----
