[ros-dev] Trunk locked
timo.kreuzer at web.de
Mon Aug 2 17:27:33 UTC 2010
To get trunk in a good state as soon as possible, it's important that we
all pull together.
I appeal to everyone to stop working an any fancy features (in the
branches, too) and instead have a look at bugzilla. We have 36
regressions there. And there's also a wiki page:
I started assigning the bugs to the ones who have probably caused them.
(Please don't take offense, this isn't supposed to mean that this person
did something wrong, but is the one, who is most likely capable of
working on a proper fix)
A number of regressions still have no causing revision. We should try to
find out these revisions if possible. I think our testers should
I also set priorities to P1 or P2 for regressions.
It's important that everyone checks his bugs, especially those with
priority P1 and see if he can fix it.
If you have such a bug assigned and cannot fix it, think about reverting.
If that's not possible either we need to find another solution.
Ignoring it will not make it go away.
Maybe we can make trunk *rock solid* before we add anymore features.
Then we can make a good release and everyone is happy.
Happy bugfixing everyone :D
PS: For those who don't like to work with the bugzilla webpage, we have
a license for Deskzilla for reactos. I'm using it regularly. But please
don't use it for write access. Due to a bug in can cause massive
More information about the Ros-dev