Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3D8F7611.CE166883@phekda.freeserve.co.uk>
Date:	Mon, 23 Sep 2002 21:14:09 +0100
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: DJGPP 2.04 status page up
References:	<3D8DA9EA DOT 5EA3E23 AT phekda DOT freeserve DOT co DOT uk> <003201c262e8$4aea29b0$0100a8c0 AT p4>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Andrew Cottrell wrote:
[snip]
> The status page has the following line could in some circumstances give a
> wrong indicated that GCC 3.2 is broken:-
>     Problems with rm.exe and the gcc 3.2 build.
> I suggest changing it to:-
>     Problems with file utilities when built with CVS LIBC cause rm.exe
> failures whichin turn cause GCC 3.2 build issues (not GCC related).

Done.

> Statuis page change suggestions:-
> 1) How about a section for reported, but not investigated issues?

Done.
> 2) How about prioritzing the issues somewhere so that people can see what
> the major issue is? This is very subjective and if you have traced my status
> page I never seem to get to Rhide as a showstopper always comes out of left
> field just as I get close to looking at Rhide....next weekend Rhide...no
> rm.exe...doh....

Sure. What priorities should we use? How about the following:

1 - Showstopper: Must be fixed before shipping alpha, beta or final
2 - Major: Must be fixed before shipping 2.04
3 - Minor: Should be fixed before shipping
4 - Nitpick: Would be nice if it's fixed before shipping, but quite possibly
will never be fixed

If the bug tracking system has priorities, we probably should use them. (I
haven't looked at the bug tracking system yet.)

> 3) I think that the page should reference the 9 outstanding DJGPP bugs from
> the bug tacking system. Some may be able to be closed in order to reduce the
> number.

I will reference them.
 
> Some comments on the files at clio:-
[snip]
> 4) The build takes about 2 to 3 hours and then the upload takes anywhere
> from 8 to 30 hours of time to do on the 56K modem. I have been looking at
> ADSL, but it costs $AUD60 (approx $USD30 for 1GB/ month at 256/128).

Ouch. That must be slow. I'm on the end of a 56k modem too. Perhaps we can
both autobuild all the packages, but only upload half each? That way we'd save
on the 'phone bill and get more testing. ;)

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -