https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10407
--- Comment #52 from Tomás Cohen Arazi <[email protected]> --- (In reply to Pete Edwards from comment #51) > OK - I see the point about most of my question and will raise it on devel. > But, isn't this the correct place to point out when a patch causes a > regression problem. It is breaking an existing API. There are a couple options for you on this issue: - File a bug explaining the regression and requesting it to be fixed. You need to set the 'depends on' field to this bug number. Beware that others migt consider the change is ok and close the bug as WORKSFORME. API changes are not usually considered a bug, but an enhancement. But this is just a matter of discussing (dis)advantages and reaching a middle ground. If there's a regression it is always a good practice to provide a regression test patch. - Comment on koha-devel the 'general' situation, in which there's an API change that should be better explained on the release notes. Which I would agree with BTW. Looking forward to this discussion! -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
