From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10209171450.AA16719@clio.rice.edu>
Subject: V2.04 work list (was... status page)
To: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date: Tue, 17 Sep 2002 09:50:03 -0500 (CDT)
Cc: rich AT phekda DOT freeserve DOT co DOT uk (Richard Dawe), djgpp-workers AT delorie DOT com
In-Reply-To: <007401c25e2d$1789eed0$7397adcb@p4> from "Andrew Cottrell" at Sep 17, 2002 07:31:36 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

> > As far as I can tell from looking at mails in my todo folder, the only
> > major issue is the one with rm on Windows 2k/XP. Plus lots of testing!

I don't really think that's quite true - we need to come up with a list of
what's in - what's out - and discuss.  For example, something like making
sure the library and headers are compliant with newer versions of the C
standard.  What to do about iconv in packages.  The new malloc package.
Image size (should we UPX the distributions?).  Dynamic linking of libc.
Wide chars?  Compatibility with application distributions, etc ...

> > vital features, features that may go in, features that will go in
> > 2.05/whatever is next, known bugs, what needs doing, etc.
> 
> Looking forward to seeing the web page.

I also - finalizing the scope is always the first step for a release :-)

In some cases just documenting limitations on Win2K/XP may be the best
we can do.

Remember, the clio web page started out as a Win2K/XP issue center, and
V2.04 is much more than Win2K/XP compatibility (especially with 2.03
refresh on Simtel).