Hi,

I'd like to push back the freeze for a few days for the following reasons:
a) I'm not completely sure about how the Win32 port should be
  handled (regarding the release). Petr has put a lot of work into getting
  things up and running on Win32, but he hasn't had the time to finish
  his work on the DirectDraw driver yet.
  I don't know whether a few more days will fix that, but, at the very
  least, they should allow us to discuss this issue.
b) I'd like to have a closer look at some of the remaining bugs
  first. The "stopping movement" bug (CB1, also KQ4 and HQ) can probably
  be fixed without any major changes (i.e. during the freeze), but the
  CB1 purse (see my next mail) might require some of those.


Please note that FreeSCI 0.3.1 won't be without known bugs. That's what
the 0.4.0 (beta) and, eventually, 0.5.0 (stable SCI0) series are for.

Unless there are any objections, we should start freezing on wednesday
(that'll give us three more days) and release on thursday the week after
(I won't have time to test/package anything or update the homepage on
wednesday). 3 days for medium-sized changes, and 8 days for
testing, updating the docs, and fixing minor stuff.


Another thing: There has been some interest lately in starting to work on
an interpreter with more memory (as required for SCI01 and SCI1) in
parallel to the things we need to do after 0.3.1 (bugfixes, DoAvoider(),
config screen, on-screen display, glx or xlib or sdl target, and, most
importantly, sound). Is there still interest in this? If so, any
suggestions regarding how this should be done?

We have the following options:
a) Completely separate development (as with the GFX subsystem- only works
if no more than one or maybe two people are working on it. Same problems
as b)
b) Separate CVS branch (Changes wouldn't damage the stable VM, but fixes
and improvements to the stable branch would have to be forward-ported)
c) Same CVS branch (would require VM to be swappable at compile or run
time, more work, potential damage to the stable VM, but easier testing and
no need to apply any changes to two branches)

llap,
 Christoph


Reply via email to