Thanks Jason. I appreciate that everyone on the list has a day job too, but it *is* very frustrating to report an issue, document it well, provide test cases and a patch and have it sit around without any visible action being taken on it. I was kind of hopeful that this issue would have been resolved sooner due to its simplicity (its easy to see from a code inspection that there is a bug IMHO), but I understand the velocity required to validate changes.
Too much frustration trying to get bugs fixed will result in less input from users, putting more burden on the developers. Changes in the feature set are a bit different, but prioritizing issues that are bugs, based on whether there is a patch containing a test case and/or a fix would lower frustration and also encourage greater investment from the user community. If I knew the the bug that was really annoying me was going to get priority if I put in the extra time to provide a testcase and a fix, I'd be more inclined to spend the time. To make it effective, the method of prioritization would need to be made public and would need to be enthusiastically followed by the development team. William -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Tuesday, 7 August 2007 12:48 AM To: Maven Developers List Subject: [***POSSIBLE SPAM***] - Re: Please apply the patch for WAGON-73 - Email has different SMTP TO: and MIME TO: fields in the email addresses On 6 Aug 07, at 12:18 AM 6 Aug 07, William Ferguson wrote: > Come on guys. > The patch is the addition of just 2 return statements. > There's really not much to verify here. > > And 2 additional (simple) test cases have been provided. > Surely that in itself is a good thing to add to the code base. > > Now that Joakim has unassigned himself from the issue, can someone > please pick it up and apply the patch? > I will try it, bootstrap maven and try the usual set of tests. This is typically why it's not a speedy thing as to validate even small changes as we have to run through the whole process to make sure it works. I've applied patches that seems minimal they end up inadvertently making something else not work. Don't get frustrated, the patch is simple yes but we all have day jobs just like you. > William > > -----Original Message----- > From: William Ferguson [mailto:[EMAIL PROTECTED] > Sent: Friday, 3 August 2007 11:39 AM > To: [email protected] > Subject: Please apply the patch for WAGON-73 > > This issue is a real pain : http://jira.codehaus.org/browse/WAGON-73 > > There are test cases for it and there is a patch for it. > All of which were provided in May. > > Could someone, please, please apply the patch. > > Willliam > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
