https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24153
--- Comment #7 from Julian Maurice <[email protected]> --- (In reply to Jonathan Druart from comment #6) > Yes it will need to be advertised correctly in the release note. Can it be written now in "Text to go in the release notes" ? :-D > I think it makes sense to force the --confirm flag to effectively make the > changes, it's what we do in most of the other scripts. I agree that it makes sense. This script removes data so we should prevent unwanted data loss. I just don't like breaking changes :-) I kind of like the `git clean` approach which requires a flag (-n, -f or -i), which forces users to read the documentation first. Maybe we can have similar behavior for scripts that remove data (just a thought for future scripts, not blocking) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
