On Wed, Apr 03, 2013 at 22:22:12 +0100, Aaron Gray <aaronngray.lists@xxxxxxxxx> wrote:
I am a C/C++ coder and would love to be brought up to speed with what is required to be able fix bugs and problems in new releases for the hardware I posse. It seems things do get broken or left behind all too often. The nice IBM PowerPC based RAID cards in my older Fujitsu-Siemens 970's worked to FC9 then stopped and started working again in F14. Something to do with kudzu and hardware probing, but I never found out why in the end which was frustrating.
As noted in other replies timely testing. It is a lot easier to be successful getting something fixed if breakage is reported very shortly after the change that broke it.
Finding the change that broke it yourself (say using git bisect) is also helpful as it points developers at exactly where the problem is in most cases. (Saving them time that can be used to consider how to fix the problem.)
Being able to supply patches for fixes is even more valuable. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
