X Strike Force XFree86 SVN commit: r1895 - /
Author: branden
Date: 2004-09-28 13:01:56 -0500 (Tue, 28 Sep 2004)
New Revision: 1895
Modified:
HACKING
Log:
Add a step to the release checklist.
Modified: HACKING
===================================================================
--- HACKING 2004-09-28 17:51:34 UTC (rev 1894)
+++ HACKING 2004-09-28 18:01:56 UTC (rev 1895)
@@ -414,6 +414,26 @@
never seen them installed before.
+ Use a chroot to test purges of every package. (Purging is a strict superset
of removal, so this exercises normal removal as well.)
+ + If it is getting close to Debian distribution release time, or you want to
+ earn your stripes as a quality-assurance badass, do the following as well:
+ - Use a chroot to test upgrades of every package from the latest stable
+ release.
+ - Use a chroot to test downgrades of every package back to the latest stable
+ release.
+ Broken upgrades from stable to unstable are very bad news. Earn the respect
+ of the Debian Release Managers and the admiration (well, okay, grudging
+ tolerance) of mixed stable/unstable users by ensuring that users of the
+ previous stable release can upgrade to what's in unstable. Because package
+ dependencies will likely cause many non-XFree86 packages to be upgraded as
+ well, it is possible this test will fail through no fault of the XFree86
+ packages you have just prepared. If this is the case, it's not a
+ showstopper for the XFree86 package release. Waste no time in reporting a
+ bug against the package that is causing the problem. If one has already
+ been filed, point out that the bug breaks XFree86 upgrades as well. Stable
+ users can and will upgrade to unstable version of XFree86, usually in
+ the hope (occasionally in vain) that the hardware support will have improved
+ -- it's a simple fact of life. Bring any such externally-caused breakage to
+ the attention of the Debian X mailing list.
* If the package has built and passed muster with the above battery of tests,
sign and upload the release.
Reply to: