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
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?
Thanks Steven
__________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
we already have some part of directx working in reactos the graphic system of directx like directdraw and directd3d will maybe come after 0.3 but I am planing gettin the win32k ready for d3d after that I think it is egunt with dx support for 0.3
----- Original Message ----- From: "Steven Edwards" steven_ed4153@yahoo.com To: ros-dev@reactos.org Sent: den 17 November 2005 05:34 Subject: [ros-dev] 0.3 release plan - Again
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
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?
Thanks Steven
Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.3/172 - Release Date: 2005-11-15
I'd like to recommend that releases after 0.3 be focused on stability. If an application makes a bad call/isn't compatible/whatever it shouldn't take down the whole system.
Magnus Olsen wrote:
we already have some part of directx working in reactos the graphic system of directx like directdraw and directd3d will maybe come after 0.3 but I am planing gettin the win32k ready for d3d after that I think it is egunt with dx support for 0.3
----- Original Message ----- From: "Steven Edwards" steven_ed4153@yahoo.com To: ros-dev@reactos.org Sent: den 17 November 2005 05:34 Subject: [ros-dev] 0.3 release plan - Again
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
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?
Thanks Steven
Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.3/172 - Release Date: 2005-11-15
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I am waiting with bated breth for 0.3. I have a test system that is waiting for USB. As soon as USB is working I will put ROS on my real hardware for testing.
I hope this will be a help to the group.
On 11/17/05, Richard Campbell eek2121@comcast.net wrote:
I'd like to recommend that releases after 0.3 be focused on stability. If an application makes a bad call/isn't compatible/whatever it shouldn't take down the whole system.
Magnus Olsen wrote:
we already have some part of directx working in reactos the graphic system of directx like directdraw and directd3d will maybe
come
after 0.3 but I am planing gettin the win32k ready for d3d after that I think it is egunt with dx support for 0.3
----- Original Message ----- From: "Steven Edwards" steven_ed4153@yahoo.com To: ros-dev@reactos.org Sent: den 17 November 2005 05:34 Subject: [ros-dev] 0.3 release plan - Again
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
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?
Thanks Steven
Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.3/172 - Release Date:
2005-11-15
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- David Johnson http://www.davefilms.us
David Johnson schreef:
I am waiting with bated breth for 0.3. I have a test system that is waiting for USB. As soon as USB is working I will put ROS on my real hardware for testing.
you could always try an ISO from: http://svn.reactos.org/
Would "USB working" also mean "boot from USB" ? Not even MS allows this. Sadly no PC BIOS supports "boot from FireWire", like Apples do. Guess we'd need LinuxBIOS for that, as current motherboard manufacturers don't want to pay AMI/Phoenix/Award for including the "boot from firewire" module.
Bernd
Bernd Blaauw schrieb:
David Johnson schreef:
I am waiting with bated breth for 0.3. I have a test system that is waiting for USB. As soon as USB is working I will put ROS on my real hardware for testing.
you could always try an ISO from: http://svn.reactos.org/
Would "USB working" also mean "boot from USB" ? Not even MS allows this. Sadly no PC BIOS supports "boot from FireWire", like Apples do. Guess we'd need LinuxBIOS for that, as current motherboard manufacturers don't want to pay AMI/Phoenix/Award for including the "boot from firewire" module.
The thing with the LinuxBIOS sounds interesting, I heard about it some time ago. Do you know, if it is working on current mainboards and where I can get some more infos about this topic? Maybe we could create a BIOS replacement out of freeloader, this would enormously increase the boot-process...
Bernd
Greets,
David Hinz
David Hinz schreef:
The thing with the LinuxBIOS sounds interesting, I heard about it some time ago. Do you know, if it is working on current mainboards and where I can get some more infos about this topic? Maybe we could create a BIOS replacement out of freeloader, this would enormously increase the boot-process...
guess w're going a bit offtopic.
Just like ReactOS, the LinuxBIOS project has a huge WIKI (as frontpage even): http://www.linuxbios.org/index.php/Main_Page
if ReactOS will be coded properly, it should be able to run either under LinuxBIOS natively, or using Linuxbios + ADLO (some Bochs modules on top of LinuxBIOS).
Interesting thing ofcourse would be LinuxBIOS + XEN (+hardware virtualisation support) + any (compatible) operating system.
I'm following progress of both ReactOS and LinuxBIOS, but am not a coder at all. This LinuxBIOS thingie seems to be in development on AMD K8 platforms nowadays. Sadly, there's no 440BX port, otherwise it could act as the BIOS for an emulator (even VMware allows external BIOS files for their emulated 440BX)
Bernd
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
Hi, Steven Edwards wrote:
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.2.9-rcX to 0.2.9
0.3.x - OpenGL games, Firefox, Mirc, OpenOffice, third party drivers, start of PnP, USB, Xbox support, Initial DirectX Support, etc
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
Yes, these are show stoppers, so to keep the public happy we are going to need to release RCx's before 0.2.9.
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?
Thanks Steven
8^D James