"Thomas Dukleth" <[EMAIL PROTECTED]> wrote: > 2. STANDARDS OF BUG SEVERITY. > > For the benefit of those who were not present or do not remember, Joshua > Ferraro offered a standard for bug severity on the #koha IRC channel in > which almost any bug which was noticed by the librarian would be perceived > as critical. [...]
I support our current descriptions, which you can find at http://bugs.koha.org/cgi-bin/bugzilla/page.cgi?id=fields.html#bug_severity Blocker Blocks development and/or testing work Critical crashes, loss of data, severe memory leak Major major loss of function Minor minor loss of function, or other problem where easy workaround is present Trivial cosmetic problem like misspelled words or misaligned text Enhancement Request for enhancement I'd suggest that the "librarian noticability" aspect would be better represented by the bug's Component and possibly the Priority. > 3. APPLICATION TO VERSION RELEASES. > > The problem here is that libraries are concerned about either how they are > perceived through the software they use or suspicious of deeper problems > in software when even superficial bugs are noticeable. [...] To allay that suspicion, we should be clear in our release notes that what should be our full list of known bugs is public and available. Hope that helps, -- MJ Ray (slef) Webmaster for hire, statistician and online shop builder for a small worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
