[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[address@hidden: platform-testers]
From: |
John Darrington |
Subject: |
[address@hidden: platform-testers] |
Date: |
Sat, 29 Aug 2020 11:06:59 +0200 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
----- Forwarded message from Jeffrey Walton <noloader@gmail.com> -----
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 -----
- [address@hidden: platform-testers],
John Darrington <=