Bug Tracker

[Boriss Mejias]

Dear hackers,

One of the part that is still missing from the migration of the 
development infrastructure is the bug tracking system. As we mentioned 
before, there is no automatic way of moving the bug reports from the old 
system to the new one.
http://gforge.info.ucl.ac.be/tracker/?atid=149&group_id=17&func=browse

The only solution I see now, is to move by hand all the open bugs. There 
are not too many (see list bellow), but we will need volunteers for this 
not so amusing task. I would start only with volunteers having already 
an account in the current bug-tracking system. If we don't have enough, 
we can ask volunteers within users.

If somebody has a suggestion about what to do with the report of fixed 
bugs (661) it will be appreciated. For the trashcan, I don't see 
anything better that just ignore it. Note that the "incoming" track has 
9999 entries. I'm quite sure that no more that 15 are actually bug 
reports. The rest is just spam or mail delivery error messages.

While we get some volunteers, I would like to discuss some of the 
categories. But we will do that later.

Here is the information I collected from
http://www.mozart-oz.org/cgi-bin/oz-bugs
I volunteer to start recovering "incoming" bugs.

cheers
Boriss

FIXED		661
LIMITATION	39
MOGUL		0
OBSERVATION	7
PENDING		5
REQUEST		24
RETIRED		18
TRASHCAN	1272
compiler	8
configure	3
constraints	13
contrib		0
darwin-ppc	3
debugging	2
demos		1
distribution	8
documentation	14
engine		1
incoming	9999
libraries	5
linux-hppa32	0
linux-i486	0
misc		0
mozart-gtk	3
netbsd		1
ozmake		6
solaris-sparc	0
tools		7
win-i486	12