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

--- Comment #32 from mathieu saby <[email protected]> ---
(In reply to Pierre Angot from comment #30)
> Well, I'm agree and disagree ^^
> 
> I'm ok with the goal. It's fine, but I prefer having a warn message on item
> deletion when AcqCreateItem is "when placing an order".
> 
> You've mentionned a new patch. It will be a good thing if this new patch
> blocks this one.
> 
> Is it possible ? It's easy to test on sandbox, I can sign both of them
> rapidly.

Hi Pierre
I agree that an other patch could be made for improving Koha's behavior when
you try to supprss items, but : 
1/ it is better to write small patches, each one adressing a specific issue
(even if we can link bugs together or maybe create a wiki page for grouping
patches about the same kind of issue). More easy and quicker to test, sign off
and QA.
2/ the patch for adding warnings when you suppress items is not written yet
3/ maybe the logic for this new patch should be slightly different from 9780,
so we need to make some specifications first, have discussion, etc, and it will
take time - wile 9780 is already signable.
4/ as Paul Poulain wrote in a message to french list recently, there's
necessarily a "selfish" dimension behind community involvment, especially when
you write patches on week-ends, not beeing paid for that (and you know that's
my case). So I wrote this one for "my" librarians, because for us - we create
items at receipt - deleting records linked with orders is a bigger issue than
deleting items linked with orders. Maybe I could have time to write the other,
maybe not...

For all those reasons, I say to "Signe, boulet!"

Mathieu

-- 
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/

Reply via email to