<html><head/><body><html><head></head><body>I'd obviously prefer not to have one set of eyes less. But if it is just bug fixes to help reduce the bottleneck then I will suspend my objections :) <br>
<br>
Chris <br><br><div class="gmail_quote">Jared Camins-Esakov <jcamins@cpbibliography.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">Good morning.<div><br /></div><div>I thought about using the subject "In search of lost time," but I decided that was a bad idea given how few people actually manage to get through Proust.</div><div>
<br /></div><div>I am writing with a discussion question for the community. According to the dashboard, at the moment we have 120 bugs with the status "Needs signoff" (25% of these are classified as "bugs" instead of "enhancements" or "new features") and 94 bugs with the status "Signed off" (50% bugs). 2 bugs have the status "Passed QA" and are waiting for feedback from their authors before I push them.</div>
<div><br /></div><div style="style">There are two lessons we can learn from these numbers:</div><div style="style">1) if everyone currently involved with Koha made a commitment to test two patches in January, we could get through the backlog for 3.12</div>
<div style="style">2) we have a QA bottleneck.</div><div style="style"><br /></div><div style="style">Please consider lesson 1, but this e-mail is actually about lesson 2. QA is an inherently time-consuming process, and the pool for QAers is much smaller than that for signing off. I expect that as we approach the deadlines for 3.12 the number of bugs awaiting QA will decrease. Unfortunately, the amount of time I have to deal with those bugs will not increase, even though I am spending somewhat less time than I planned dealing with RM duties this month. So, I come to the community with a question: what would people think of me using that time to QA bugs (as opposed to enhancements/new features) that I was not involved in the authorship or signing off of? I would prefer not to do this, but after a month and a half as RM it seems to me that this might be in the best interest of the community and the best way to release a stable and feature-full 3.12. QAing signed off patches wou
ld
naturally take a much lower priority for me than addressing patches that have already passed QA, but every patch I QA is a patch that our overworked QA team does not have to QA.</div>
<div style="style"><br /></div><div style="style">Thoughts?</div><div style="style"><br /></div><div style="style">Also, on a somewhat-related subject, I will be away from January 25-February 4. Keep that in mind if you intend to have any questions that only the RM can answer at the end of the month.</div>
<div style="style"><br /></div><div style="style">Regards,</div><div style="style">Jared Camins-Esakov</div><div><div><br /></div>-- <br />Jared Camins-Esakov<div>Bibliographer, C & P Bibliography Services, LLC</div><div>(phone) +1 (917) 727-3445</div>
<div>(e-mail) <a href="mailto:jcamins@cpbibliography.com" target="_blank">jcamins@cpbibliography.com</a></div><div>(web) <a href="http://www.cpbibliography.com/" target="_blank">http://www.cpbibliography.com/</a></div>
</div></div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px"><hr /><br />Koha-devel mailing list<br />Koha-devel@lists.koha-community.org<br /><a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br />website : <a href="http://www.koha-community.org">http://www.koha-community.org</a>/<br />git : <a href="http://git.koha-community.org">http://git.koha-community.org</a>/<br />bugs : <a href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a></pre></blockquote></div></body></html></body></html>