|
From: | paul POULAIN |
Subject: | Re: [Koha-devel] Bug questions from meeting |
Date: | Fri Aug 8 08:39:03 2003 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 |
MJ Ray wrote:
definetly yes. It's a good idea, that could solve my yesterday mail (subject : [important] for bugreport & templates).http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=557 seems to be specific to a single site. How should we handle it? It seems that we will have a fix for http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=561 today but should there be a category for "Templates"?
<slef> It would be great if we can catch any half-fixed bugs before 2.0.0 <slef> 2.0.0pre2 was released on 9 July <slef> The bug life cycle is something like: reported -> NEW -> ASSIGNED -> RESOLVED -> VERIFIED -> CLOSED <slef> right now, we're not getting that many reports, but things seem to go from NEW to RESOLVED quite quick and they get stuck there just now. <slef> owen: oh, small point: the developers of that part of koha should not be the ones to mark a bug VERIFIED I think
- Shouldn't we nominate slef as QA coordinator ?- 100% agree with all those ideas (including me never marking bugs verified/closed :-) )
PS : sorry for not being there on last wednesday. I must apologize, coz my reason was... beach 8-) It's really hot, hot in France (35-37°C everyday) so, almost on every afternoon, we go to he beach, and have dinner here. I'll try to be on next meeting, then 15days off (from august, 15 to september, 2)
-- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
[Prev in Thread] | Current Thread | [Next in Thread] |