> I'll admit that I don't really understand the procedure for signing off and
> testing for new features.
There are a few steps before a patch can make it into a release. We
should do a Schoolhouse Rock about it.
1. A patch is submitted.
2. Someone tests the patch. If it works, the person signs off on it,
meaning they personally attest to the patch's usefulness.
3. The QA manager ("Quality Assurance") tests the patch again and
confirms that it works, that code meets project standards, etc. If the
QA manager approves, the patch is "Passed QA." The QA manager only
looks at patches which have at least one sign-off.
4. The Release manager then does his own examination of the patch and
if he also agrees the patch is "pushed," or added to the next release.
The RM only looks at patches which are passed QA.
> The one we are interested in is "Analytics
> records support"
> http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5528
> which has the Patch status of "Signed off" and was modified on 2011-09-21
> but isn't on your list.
So the QA manager hasn't yet examined that patch. The feature is still
awaiting his approval.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
