Release notes for Koha new versions and maintenance versions are build automatically based on Git repository commits and Bugzilla info. A script named get_bugs.pl from release tools do the job.
In the release notes, 4 info from BZ are used: - bug id - summary -- short description of the bug - component: equivalent of Koha module (Acquisition, Web Service, etc.) - severity: critic, normal, new feature, etc. A fifth info can be retrieved in order to describe in detail the bug/feature. This is just the first BZ comment. The first comment can't be changed later in BZ. So very often the 1st comment doesn't describe properly the bug. In order to improve the readability and usefulness of release notes, couldn't we: - Try to normalize and improve the bug summary field when the patch is pushed to master - Add an optional BZ custom field named releasenotes for example, which would contains useful info describing the bug in detail when necessary. _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
