I really don't mind if the build is broken occasionally. We know that we will have major changes to the tree in the next few weeks, and it will be impossible to avoid regressions in the code or in the build.
However, a couple of things will help:
1) Before someone knowingly breaks the tree, they should warn everyone to stop updating their cvs copies until it is fixed again. That way they can continue to work on their features/bugs.
2) Try to limit the scope of the breakage. If it can be limited to a directory or two, please do so. Break it, fix it, then break it again later.
Too bad we are not using Subversion. It would be so handy to be able to tell everyone which revision number is the current working version.
Bob
Felix Rabe wrote:
Hi all,
I agree that the CVS code should remain usable, but (not blaming anyone!) I don't think it is a productive way to then put everybody under pressure to fix every crash by yesterday.
I just want to remind you (as an outsider and non-developer; I actually don't have any say here) that this project came into existence to grant more freedom to its developers. If you expect to have every bug fixed ASAP in (by nature) shaky code, you will start to drive people away again if you get used to this behavior.
Just want to remind you *before* it becomes a serious problem.
Greetings and happy hacking,
- Felix