With the TC function description settled, it's time to elect a Testing Coordinator. I'd like to nominate Andrew Munger aka WaxDragon for this position. Voting will start 7 days from now and the vote will run for 7 days.
Gé van Geldorp.
Thanks for the nomination, Gé, I accept. However, there are a few things I would like to say.
First, I'm not sure I can spend as much time doing TC duties as I did previously. I will be able to do testing "at a reasonable pace", and the reduction of time for manual testing has prompted me to seriously think about the beginnings of automated testing. I have several ideas that I wish to discuss with the team.
Second, I am really dismayed by what has happened to trunk while since I stopped testing it. I know there is a progress and regress cycle that we seem to operate on, but this is one of the worst breakages I have since since following the project. Two months ago I called for a tree freeze, and it wasn't as broken as it is now. I know that alot of it stems from the PnP work, which is good, but I thought PnP was further down the roadmap. These breakages have delayed the progress towards 0.3.0, IMHO. It's a tough call, since PnP will help with NIC support and installation. Those in IRC know I've been experimenting with a multi-homed config, in hopes of getting a ReactOS based router going.
I also ask that all svn committers try to assist my in my duties, by testing patches before committing, and using branches when necessary. In return, I will be open to any suggestions regarding the testing procedures. Together we can make ReactOS great!
WD
On 11/8/05, Ge van Geldorp gvg@reactos.org wrote:
With the TC function description settled, it's time to elect a Testing Coordinator. I'd like to nominate Andrew Munger aka WaxDragon for this position. Voting will start 7 days from now and the vote will run for 7 days.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- <mikedep333> but if it isnt working, why is it even included on the CD?
Hi Wax,
--- WaxDragon waxdragon@gmail.com wrote:
of it stems from the PnP work, which is good, but I thought PnP was further down the roadmap. These breakages have delayed the progress towards 0.3.0, IMHO. It's a tough call, since PnP will help with NIC support and installation. Those in IRC know I've been experimenting with a multi-homed config, in hopes of getting a ReactOS based router going.
The good thing about work on both being done now is the cycle from 0.3 to 0.4 will be short. In my view we are very close to being able to tag 0.3 now that firefox is sorta working. Its not like we are promising 0.3 to be super stable or be able to support networking on anything other than VMware/Qemu.
In my mind we should try to nail down all the regressions that have anything to do with networking. Figure out whats left to fix and stick a fork in 0.3 and focus on 0.4 which will feature
- True plug and play - Real stablity
I also ask that all svn committers try to assist my in my duties, by testing patches before committing, and using branches when necessary. In return, I will be open to any suggestions regarding the testing procedures. Together we can make ReactOS great!
Amen!
Thanks Steven
__________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com