launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #09276
Re: Submitting a patch docs missing info about QA process
-
To:
Launchpad Community Development Team <launchpad-dev@xxxxxxxxxxxxxxxxxxx>
-
From:
Steve Kowalik <steve.kowalik@xxxxxxxxxxxxx>
-
Date:
Thu, 19 Apr 2012 22:01:18 +1000
-
In-reply-to:
<CAHZ8tnZMqVP8dUJnQVRceFwqECvYavusx9w4nVoepm7na7e=7w@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
On 19/04/12 20:22, Jonathan Lange wrote:
> Cool. I can't quite figure out how to write this up on the dev wiki,
> and would very much appreciate it if one of the Canonical
> Launchpadders could do so. There needs to be something about QA
> because anyone submitting patches to LP actually cares about getting
> them released, not about getting them landed.
Agreed. Personally, I always smile a little when I see that I can
reproduce a bug on production, and can't on qastaging, which tells me
I've fixed it, and the code and tests I wrote were worth it.
I think we should encourage casual contributors to do their own QA, but
codify in the guidelines that it isn't required, and if they don't feel
comfortable doing their own QA they should hand off to an Launchpad
developer.
Cheers,
--
Steve
Launchpad Developer
Canonical, Ltd
References