From mint-bounce@lists.fishpool.fi Mon Sep 13 14:04:50 2010 X-Virus-Scanned: amavisd-new at demon.co.uk Subject: Re: [MiNT] 1.17 release From: Alan Hourihane To: Helmut Karlowski Cc: "mint@lists.fishpool.fi" In-Reply-To: <270906.400258781-sendEmail@descaro> References: <270906.400258781-sendEmail@descaro> Content-Type: text/plain; charset="us-ascii" Date: Mon, 13 Sep 2010 19:02:18 +0100 Message-ID: <1284400938.10680.11.camel@jetpack.demon.co.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: alanh@fairlite.co.uk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Mon, 2010-09-13 at 17:50 +0000, Helmut Karlowski wrote: > Alan Hourihane wrote: > > > On Mon, 2010-09-13 at 17:27 +0000, Helmut Karlowski wrote: > > > Alan Hourihane wrote: > > > > > > > On Mon, 2010-09-13 at 12:13 +0200, Peter Slegg wrote: > > > > > What is happening with the planned release ? > > > > > > > > > > I am only aware of 1 minor bug at the moment, the non-topping > > > > > of windows that seems to mostly affect Toswin2 and Thing. > > > > > > > > I guess documentation. > > > > > > > > Until people are happy with that, I got the feeling people didn't want > > > > to release. > > > > > > I'd say do a release asap. Or wait 'till end of days when the CTPCI-users have fixed > > > their computers. Development is slowed down when there is no official > > > version (which would be current trunk). > > > > > > We are long overdue! > > > > Indeed, but people are complaining of graphics bugs on this list and if > > we can't get that sorted, we've probably no hope for the wider audience. > > These are for sure specific to their system. I traced an error that Lars > Schmidbauer had on his CTPCI, and finally (he) found that it could be > solved by other fvdi-settings (no accelerated polyline). > > Also there seems to one other CTPCI-user with no problems, I wonder why > these guys ask for MiNT/XaAES-fixes instead of asking the other users > who have it running. > > There is also a chapter for "odd harware" in the wiki, but no one enters > his knowlegde there. It's always an XaAES-bug - silly! > > I would really not wonder about any malfunction when even the opnwk does > not work correctly. But the question is, "did it work in previous release?" If it did, why not now ? Alan.