[Mapserver-dev] Bug status needs attention

[Sean Gillies]

On Oct 6, 2004, at 3:05 PM, Daniel Morissette wrote:

> Frank Warmerdam wrote:
>> I would leave it NEW - but then I really would mean I am ignoring it.  
>>  :-)
>
> Um... I don't think that's what Sean had in mind.
>
>>> So I'd be happy to review and mark bugs assigned ASAP, as long as  
>>> the developer is also required to provide a quick analysis and ETA  
>>> as he accepts it.
>> Well, we know that not many of are "required" to do anything.  I  
>> certainly
>> go through phases when I don't spend any time on MapServer related  
>> work
>> because I am very busy on non-MapServer issues.
>
> True. We have to recognize that most contributors are volounteers  
> and/or can be very busy on other stuff at times. I am in that boat as  
> well, that's why I probably have more bugs untouched (in NEW state)  
> than anyone else.
>
> But if we require that bugs be set to ASSIGNED or something else as  
> you and Sean were saying then we *do* require something fromall  
> developers. I didn't bring up this idea in the first place, I just  
> added an extra requirement on top of yours to reduce the user's  
> frustration (quick analysis and ETA when you accept a bug).
>
> Let's see how Sean sees things. He's the one who started this thread  
> after all.
>
> Daniel

Daniel, Frank

My immediate concern is generating an authoritative list of known bugs  
in 4.2.4
without having to read and verify each bug, and email reporter and  
owner for
clarification.

Below is a query on unresolved (minus enhancement requests) bugs which  
have a
version marked 4.2:

http://mapserver.gis.umn.edu/bugs/buglist.cgi? 
short_desc_type=allwordssubstr&short_desc=&product=MapServer&version=4.2 
&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubs 
tr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_sta 
tus=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=criti 
cal&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severi 
ty=trivial&emailassigned_to1=1&emailtype1=substring&email1=&emailassigne 
d_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidty 
pe=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldv 
alue=&cmdtype=doit&namedcmd=Active+1+Day&newqueryname=&order=Reuse+same+ 
sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

Could you help me rally developers to go through this list and, where  
appropriate,
change status of bugs to FIXED, WONTFIX, or UNCONFIRMED?  Afterwards,  
I'll report
each remaining unresolved bug as a known bug whether status is NEW or  
ACCEPTED.

Once 4.2.4 is released, I'll think a bit more about how to better do  
this for
the 4.4.0 release, and about the larger issues.

thanks,
Sean

--
Sean Gillies
sgillies at frii dot com
http://users.frii.com/sgillies