Date:	Mon, 7 May 2001 18:11:11 -0400
Message-Id:	<200105072211.SAA25769@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp-workers AT delorie DOT com
In-reply-to:	<3AF6DBD7.496DE8C6@phekda.freeserve.co.uk> (message from Richard
	Dawe on Mon, 07 May 2001 18:31:03 +0100)
Subject:	Re: DJGPP 2.04 release date
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010429094950 DOT 26520G-100000 AT is> <3AF6DBD7 DOT 496DE8C6 AT phekda DOT freeserve DOT co DOT uk>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Don't we need a set of release criteria first?

No, not really.  I could make a set of zips right now and release
them.  It's not a good idea, of course.  I could say "We're releasing
2.04 on June 1" but I don't know how useful that would be (saying it,
not doing it ;).

I think what Eli means is that we've probably accumulated enough fixes
and enhancements in cvs that we should start working towards the next
release, meaning no more new features and concentrate on testing and
bug fixing.  We can also start the beta processes.  Having a specific
date to shoot for might give us some incentive also.

> * GCC 3.0 support => dependent on gcc 3.0 release;

We need 2.04 to be usable to build gcc's 3.0 branch; if we release
before 3.0 is released we'll still be OK because changes to gcc to
break 2.04 after that are gcc bugs, not djgpp bugs.

2.04 must work with the existing gcc zip too, though.

> * Win2k support;

Can someone find out the status of LFN support add-ons for NT and DOS?
It would be nice if we could recommend something.  The Zip Picker also
doesn't have instructions specific to 2k or ME (Eli is working on ME,
I think).

> What else is there?

Charles' Law: The most important bug will be found right after the release.

- Raw text -