[Koha-devel] Development/ QA protocol question

[Jonathan Druart]

In my opinion the QA queue (as well as the signoff queue actually) should
be processed by bugs severity: blocker, critical, major, others. It's a
"should be", not a "is"...
And then the new enhancements, features.

The way the patch is written, the length of the diff, the author of the
patches (yes!), the module it affects (not SIP...) are some of my personal
factors.

On Wed, 29 Mar 2017 at 12:28 Cab Vinton <bibliwho at gmail.com> wrote:

> Yes, all makes perfect sense, Jonathan.
>
> I suspect the way in which projects work their through QA is opaque to
> most libraries, and like any client, they're always happy when their
> projects get lots of attention, move through quickly, etc.
>
> I believe at any given time there are dozens of patches somewhere in
> the QA process.
>
> So from the client's perspective it would be great to have a better
> understanding of how the QA team determines which ones to work on
> first. I believe the vast majority have P5 priorities & low severity
> (i.e., are "enhancements" rather than critical or major).
>
> Thanks,
>
> Cab
>
> On Wed, Mar 29, 2017 at 11:04 AM, Jonathan Druart
> <jonathan.druart at bugs.koha-community.org> wrote:
> > The developer is supposed to estimate the cost of the development
> including
> > the QA process and the different steps of submission.
> > A (good) developer must take care of most of the project's requirements
> and
> > follow the guidelines.
> > He will also provide tests for the change he made, write a valid and
> correct
> > test plan, take care of side-effects, provide small patches, etc.
> > The longer a developer will spend during the development step (before the
> > first submission), the quicker the QA process will/should be :)
> >
> > Hope it makes sense,
> > Jonathan
> >
> > PS: QA is not an exact science...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20170329/cf7375e6/attachment.html>