Re: [MiNT] 1.17 release

[Alan Hourihane <alanh@fairlite.co.uk>]

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.