X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<55673F0B.1090103@iki.fi>
Date:	Thu, 28 May 2015 19:15:07 +0300
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi)" <djgpp AT delorie DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version:	1.0
To:	"DJGPP List (E-mail)" <djgpp AT delorie DOT com>
Subject:	DJGPP v2.05: some thoughts
Reply-To:	djgpp AT delorie DOT com

I think it would be best to get DJGPP v2.05 actual release out soon enough. It would not be nice to 
repeat what happened with v2.04 again.

Some questions that should be answered for that:
- what critical problems we have what should be fixed for release
- what we want in and what can wait

Making release would include also moving out current stuff from pub/djgpp/current (one should be 
careful with source packages) and moving files from pub/djgpp/beta to current (possibly not all) 
and other related changes.

There is danger of repeating history with v2.04 if begin to add too much new stuff or new changes.

One possible new feature that comes into mind :
- changes for more full support of wide characters have been around for a long time. We must decide 
whether we want to get it in v2.05 or we should wait after release.

One of critical problems which as I think should be fixed if possible:
- problems with DXE built with gcc-5.1.0 (I only tested 4.7.3 which is OK and 5.1.0).

There could be additional issues of course.

CVS branch for release should perhaps be created after getting possible new features in. This way 
it would be possible to continue development and avoid destabilizing 2.05 so release could be done 
in reasonable time.

Andris

- Raw text -