On Fri, 14 Sep 2001, Christoph Reichenbach wrote:
> > > 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?
I agree, let's review the current bug list, re-prioritize the current bugs
and try to eliminate the severity 4 and 5 bugs for release.
> 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.
I agree -- I would just want for Alex's work on the win32 native
soundserver to be complete (assuming it isn't already). Should we have a
more formally defined release schedule and criteria? gcc finally did this,
and it appears to be working well for them -- I know I appreciate it as a
user.
> 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.
er. please disregard this message ;>
--
http://www.clock.org/~matt
