17 Nov
2005
17 Nov
'05
1:26 p.m.
From: Steven Edwards
Hi All,
My how history repeats itself. I would like to call for a
feature freeze on Jan 1st with the approval of the Testing
Coordinator. Although we have not had that many releases of
the 0.2.x line I feel enough has changed to and that we need
to bump to 0.3. Lets review some history
0.1.x - winhello
0.2.x - explorer and a few wine dlls
0.3.x - OpenGL games, Firefox, Mirc, OpenOffice, third party
drivers, start of PnP, USB, Xbox support, Initial DirectX Support, etc
We set some goals for 0.3.0:
http://www.reactos.org/wiki/index.php/0.3.x/0.3.0. I suggest we stick to
those goals.
For the record we really did not plan on all of this
other
stuff for 0.3 and a year ago most of us would have been happy
with just Firefox and Mirc working under VMware and Qemu. In
fact we were planning on that work for the 0.3 line to be
included in 0.4 release. Which is great! I am happy to see
that we have gone much further beyond our once limited goals.
What I propose now is that everyone that has a open project
try to either get it to a Alpha state by Jan 1st or admit
that it just wont be ready for 0.3 and accept that.
Current major works in progress:
DirectX - GreatLord
USB - Fireball
PnP - hpoussin
Ws2 - Ionescu
msvcDDK - sedwards
Can we get all of these in for 0.3? Ws2 is a showstopper for
0.3, USB at least for the Xbox in my mind is a showstopper as
well. PnP would be really, really nice to have but if its not
ready I think we should ship anyway and plan on doing a short
run to 0.4 before we fully support PnP.
DirectX I have no idea how close it is to working and my
current pet project for MSVC/DDK and rbuild is not a feature.
I would like to be able to build ReactOS with our DDK under
msvc in the hopes of getting more developers to join the
project and improve the quality of our code but I am happy to
admit this is not a priority.
So what does everyone think? Can we shot for a feeze for Jan
1st? How does Feb 1st sound for a release?
0.2.8 was released on 29 Oct, we should aim for a release by the end of
December (perhaps branching by mid December, but that's up to the TC <g>).
If by then all the 0.3.0 goals have been met, we call it 0.3.0, otherwise we
call it 0.2.9.
I do have good hope that all the 0.3.0 goals can be achieved before the end
of the year. As for my own work, it seems to depend mostly on how often
trunk is broken. Of the last 4 weeks, I spent at least 2 and probably 3 on
debugging show-stopper problems (unable to boot, no networking etc)
unrelated to Firefox.
GvG