[Koha-bugs] [Bug 7167] updatedatabase improvements

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167

--- Comment #41 from Chris Nighswonger <cnighswonger at foundations.edu> 2012-01-06 14:02:54 UTC ---
(In reply to comment #36)

Up front, I think Ian raises some very good points.

> I've been leery about this development for a few reasons:

<snip>

> Following is my counter-proposal for what a change to updatedatabase should
> look like.  Marking as Failed QA for now.

However, I'm not sure that the correct "mechanism" here is a "Failed QA." In my
opinion QA is pretty objective. ie. does the code do precisely what it claims
to do. None of the points listed indicate that the code submitted does not
behave as advertised. They are all good points, but fall more into the pail of
the "is this the best way to do it" discussion. Maybe I'm wrong in that
thought. If so, feel free to correct me.

I fear this may set a precedent of QA "vetoing" features for reasons other than
objective code related problems. Of course, refusing to QA a feature could
result in a "pocket veto" of sorts as well. But I think that a conscientious RM
should not push any feature to master about which serious concerns have been
raised.

(For the record, this is not intended to be an indication of my opinion on the
modus operendi of a new update system. It is merely a procedural objection.)

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.