[ros-dev] Ros-dev Digest, Vol 56, Issue 8
caemyr at gmail.com
Wed Apr 8 22:56:52 CEST 2009
I`ll participate in testing team, no matter what shape or methode will be
chosen, this is above discussion. The approach should be discussed though.
In the years i`ve been with ROS, we had a remarkable increase in stability,
from the point when you had to be careful to finish up the planned test, so
ReactOS doesnt hang in the process, to the point when you actually have to
try hard to crash it. Certainly, we are stilll miles from being rock solid,
but the progress has been made. We have one primary problem with our
project: too many problems at the same time. Its not only stability (with
Mm, Cc and vfat issues) or hardware support (unimplemented PnP and HAL,
busted resource reporting), or Win32 subsystem issues Timo has pointed. At
the same time we have problems with WINE userland and their approach to
implementation, general code untidyness, header mess, miriads of old and
often undocumented hacks, on which future assumptions were made,
rbuild/compiler issues, lack of decent debugging tools, general lack of
manpower in all areas, lack of standarised testing platform as well as
problems determining our future goals or attracting more publicity. I think
you could add a bunch more.
You know what? We try to solve all of those problems at once. And yet we are
unable to finish off a single one.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ros-dev