Joshua Ferraro a écrit :
Q2 : if the script were not written, what about adding it after a 3.0 release ? would it be "yes" or "no" according to you. Probably NO in this case, it should be moved to 3.2, and presumably, 3.2 would be within arm's reach, two to three months max.
(from the patches reaching my mailbox during the night) And what about : ENHANCEMENT: SearchMember() uses "cardnumber%" wildcard - if other search-types fail ? following my path : - DB changes => none - API change => none - user experience change => none + the patch is small & add a small feature => no side effect possible (the '%' at the end has no consequences on indexed search, so on speed search, I don't see any other problem to double-check) I would have added it in 3.0.1 What about : [PATCH] bug 2386: adding newline between items in overdue notices ? (randomly choosen) following my path : same conclusion, patch accepted. I couldn't find a patch that I wouldn't apply in a 3.0 stable (maybe : [PATCH] bug 1953 [2/2]: whitespace and documentation changes), as it's useless, but it's also harmless, so I think I had accepted it anyway, to avoid some rebase problem later. imo, accepting such patches would result in lot of small improvements in Koha, without any stability reducing, and without having to wait for 3.1 release. With the idea of releasing a new version once every quarter or every 2 months. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel