r270 - mdadm/trunk/debian

[madduck at users.alioth.debian.org]

Author: madduck
Date: 2006-11-09 16:24:24 +0100 (Thu, 09 Nov 2006)
New Revision: 270

Modified:
   mdadm/trunk/debian/TESTING
Log:
udpates

Modified: mdadm/trunk/debian/TESTING
===================================================================
--- mdadm/trunk/debian/TESTING	2006-11-09 15:16:59 UTC (rev 269)
+++ mdadm/trunk/debian/TESTING	2006-11-09 15:24:24 UTC (rev 270)
@@ -1,6 +1,19 @@
-Testing new version of mdadm
-============================
+Call for help testing new versions of mdadm
+===========================================
 
+The problem with being the mdadm maintainer is that it doesn't make any
+friends but potentially quite a lot of enemies. Even though it's actually very
+unlikely that a new mdadm version causes data loss (mdadm is only the remote
+control into the kernel), people seem to exhibit unexpected reactions when
+their MD arrays with important data don't want to start anymore. In such
+a case, don't panic, don't do anything without understanding the implications,
+and consider asking for help.
+
+That said, I would appreciate if you guys helped me test the latest mdadm
+releases a bit more thoroughly. I do extensive tests myself, but as Murphy
+would be able to predict, the problem only ever occur on other people's
+machines, and I'd much rather fix them sooner than later.
+
 The easiest way to test new mdadm packages is by adding my package repository
 (i386/amd64) to your sources.list file, and configuring the APT pins
 appropriately: