delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2015/05/28/12:56:59

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Thu, 28 May 2015 19:56:43 +0300
From: "Eli Zaretskii (eliz AT gnu DOT org)" <djgpp AT delorie DOT com>
Subject: Re: DJGPP v2.05: some thoughts
In-reply-to: <55673F0B.1090103@iki.fi>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83twuwwshg.fsf@gnu.org>
References: <55673F0B DOT 1090103 AT iki DOT fi>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> Date: Thu, 28 May 2015 19:15:07 +0300
> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi)" <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

I'd suggest to build as much of GNU packages as possible with v2.05,
and see if they build OK and work (run test suites for those which
have them).  This should be a good test of the stability and good
shake-down of any remaining bugs.

> 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.

It's a large job, so unless there's code somewhere that is ready to be
committed, I'd advise against this.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019