https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29473
--- Comment #1 from David Nind <[email protected]> --- I have created a spreadsheet from a Bugzilla query that lists all bugs pushed to master for 21.11. This will be used to: 1. Review all bugs 2. Determine if documentation changes are required, and 3. Manage documentation tasks for a release. Process for creating the initial list: 1. View the results of the Bugzilla query: https://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=runnamed&list_id=391785&namedcmd=Doc%20changes%2021.11 2. Save as a CSV file. 3. Create an editable spreadsheet using whatever online tool considered appropriate. 4. Add columns for: . Reviewed for documentation changes (Y/N) . Documentation changes required? (Y/N) . Complexity (Easy|Medium|hard) . Reviewed by . Assigned to . Notes (add any relevant notes, for example there may be several bugs related to a change that can be managed as one documentation change) 5. Review each bug and determine whether any updates are required. 6. Update the columns in the spreadsheet (apart from assigned to). Ideally, the spreadsheet is updated weekly with the new bugs pushed to master - use the GitLab mirror as new commits pushed show up in date order (https://gitlab.com/koha-community/Koha/-/commits/master), but they don't in the Gitea repository. -- 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/
