Hi,
> > On a side note: I know there's still the "PCM sound driver" thing in the
> > TODO list, but I'd vote for cleaning up (shouldn't be much more than the
> > two issues above), fixing some more bugs, and getting in shape for a
> > release in a few weeks without it. Any objections?
>
> In a few weeks? Hmmm. Recently, someone on the local LUG mailing list asked
> for good games for Linux. I pointed to FreeSCI as an option. I got a response
> from someone who said that FreeSCI was very buggy (I don't know which
> version he used) and recommended Sarien instead, for Sierra games.
Sarien has come along further than FreeSCI has, at least in terms of
stability, portability, and compatibility with Sierra. While I wouldn't
label it as being 'very buggy', it's certainly not what we want to be
FreeSCI 0.4.0 yet.
> I only found out later that he's the maintainer of the Debian packages for
> Sarien. But he's right, I'd like to get the interpreter-related bugs out
> before next version. Perhaps I'm being too optimistic.
We have 43 registered bugs ATM; some of them might be pretty tough to
figure out. While I am looking forward to doing some bug hunting in the
near future, I don't think we'll manage to become completely compatible
with Sierra SCI in a few weeks. If we do _some_ more bug fixing, we have
enough to warrant a new release, at least IMHO.
What I'm concerned about here is that if we say that we're not going to
release until all bugs have been fixed, the release would be pushed back
by several months, meaning that fewer people would test our more recent
changes. FreeSCI already has a very long release cycle-- too long, IMHO.
Traditionally, a lot of bugfixing is done in the pre-freeze period. Right
now, the bug tracker shows a grim picture, but this might (and hopefully
will) change before we release.
How about postponing this discussion for a week or two? I'm a bit out of
touch with the interpreter part and would like to get a better picture of
some of the current bugs first.
llap,
Christoph
