Users are supposed to test latest F14 mdadm update?

[Dennis Jacobfeuerborn]

Hi,
In the latest round of updates I saw this message displayed in PackageKit 
for the mdadm update:

"This update will fix bugs and other non-critical problems.

This notification was issued on 08/10/2010.

This is a bug fix update to mdadm.  Please see the various bugs for a list 
of issues that should be resolved and those same bugs for possible ways to 
test that they are indeed solved.
It is recommended that users remake their initramfs images they boot from 
after installing this update and then reboot their machine to verify that 
the new mdadm package does not prevent proper booting of their computer. 
For safety sake, it's possible to create a totally new initramfs, modify 
your boot loader configuration to add a test boot instance that uses the 
new initramfs image as the initrd, and then boot to that test image before 
updating their known working initramfs images. This update brings mdadm to 
the latest upstream git repo plus a number of specific bug fixes.  It 
addresses far more issues than the short bug list here depicts.

In order to fully test this update, users need to not only install the 
package, but also rebuild their initramfs images using dracut and then 
reboot their machine to test that the newly generated initramfs images 
still work properly on reboot (this obviously only applies to systems that 
have their root partition on an md handled raid device). This update brings 
mdadm to the latest upstream git repo plus a number of specific bug fixes. 
  It addresses far more issues than the short bug list here depicts.

In order to fully test this update, users need to not only install the 
package, but also rebuild their initramfs images using dracut and then 
reboot their machine to test that the newly generated initramfs images 
still work properly on reboot (this obviously only applies to systems that 
have their root partition on an md handled raid device)."

Apart from the duplicated last paragraph since when are users supposed to 
test updates?
Why is such an invasive and difficult procedure recommended even though the 
update merely fixes "bugs and other non-critical problems"?
If it is recommended that users rebuild theit initramfs where is the 
explanation of how to do so?
Why is rebooting the machine to see if it properly reboots considered a 
wise testing procdedure and why is there no description of what to do if 
the system *doesn't* reboot properly?

This looks like something that belongs in rawhide and not in a stable 
release. Was there maybe a mixup and this update should have gone into 
rawhide instead?

Regards,
   Dennis