==============================
C O D E - F R E E Z E
==============================
to allow for the next "stable release" 0.0.9-official.
This release will not yet feature the EvStack kernel (we will spare this
goodie for 0.1.0).
The main cause for this is having a stable base to build our "killer-demo"
Golgotha on.
So what is there to do :
1. Stop adding complex features.
Surely any additions are welcome, but for now please only such changes
which do not break anything or require complex changes all over the place.
I have not yet decided, if the recent MESA things should go in. I will
have a look, but no promises yet.
If you can port LibGGI to more platforms, you are still welcome. But take
care not to break any others.
2. Fix all the bugs.
We need a master buglist (and a maintainer for it), which contains _ALL_
known bugs (and be it "on my sukiyaki videocard with wobblegobble chipset
the foo demo displays in wrong colors").
Every author should check his drivers/libs/demos/... and try to fix
everything listed in the buglist.
Anything that can't be fixed should be documented well.
All users should try every possible misuse of GGI they can imagine and
report on any undocumented/weird behaviour they encounter.
3. Make the installation foolproof.
All users should try a complete reinstallation and report any problems
not handled by the automatic installation procedure.
4. Build a binary libggi distribution for all known platforms. There should
be a script/makefile-target to handle this task. This is vital for the
"easy installation" requirement of Golgotha.
5. Choose and make a decent set of demos which are not too big in size, but
show off GGI's capabilities. This is realted to the single-disk project.
6. Try to fix all annoyances which are there yet. The main ones I can see
are the "Bus-error-on-switch-away" behaviour (which should be changed to
"sleep-on-switched-away") and the missing GC-mapping support.
7. Make some comaptibility lists:
a) Architecture/Platform compatibility :
List all known working combinations together with the targets that
work and a list of prerequisites (like gmake etc.).
We should add this to the source tree together with detailed
instructions on how to build GGI on the particular architecture.
b) KGI graphics cards compatibility :
List all known working cards (working means all major features are
intact. If e.g. splitline doesn't work, so what, but a crash or
defective textmode is not acceptable) together with the selected
configuration. If possible submit autodetection info to me, so
I can update util/autoconfig.
c) Monitor compatibility :
List known working monitors and chosen configuration. Make some decent
"default" Monitors using VGA and VESA modes.
8. Sync code and documentation.
Improve either of them, if they do not fit together.
