https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22890
--- Comment #27 from David Cook <[email protected]> --- (In reply to Martin Renvoize from comment #13) > In fact, I'd go so far as to say it might be nice to filter out a fair bit > of the existing data that goes into the release notes.. I don't think > librarian end users actually need/want to see a record of every single 'bug' > that's made it into a release.. especially at the moment whilst there's lots > of architectural bugs going in that don't really affect end users. > > By having the two distinct fields we could more easily direct the > information to the right people. I have librarians ask me what's new in a release, and at the moment I painstakingly read through the release notes to create a condensed user-friendly version that might actually be meaningful to them. The technical release notes are useful for developers for sure. I always learn something new when I read them, as it's very challenging to stay 100% current on every patch that gets pushed to every release. -- 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/
