Hi Paul, Just replying on principle, don't take anything personally.
Regarding "you break it, you fix it," generally, it's more efficient for the person who just committed the change that broke things to create the fix, because it's fresh in their minds. This is how it works on every software project I've ever been involved in, and is true regardless of whether it's a large community project or a small closed source project.
The axiom is generally a good one, but there are exceptions to everything. Nothing is absolute... In this case, he changed a header that's included pretty much everywhere, and it broke something in some deep place that is conditionally-compiled. So I doubt the area where the build broke in this case was any fresher in his mind than in yours.
Robert isn't angry with me because I didn't submit a fix. he's angry because I said I thought he would want to test a GL3 build before tagging the release. His assertion that I should've fixed the errors came two or three escalated posts later. The thread is in the archives for all to see.
Err, I'm pretty sure he thought you should have fixed the errors long before he posted it. As you said yourself, the written e-mails don't tell the whole story of what both of you are thinking. In general, if I see a build break, I'll check if I'm able to fix it and post the fixed files. Only if the code is really obscure and I'm not sure how to fix it will I post "hey, it's broke, can Robert have a look?". I'm pretty sure Robert expects the same from others, especially if it's just a missing #include as this seemed to be...
But again, I'm not trying to defend one or the other. I'm trying to show both people that they were too harsh.
That said, I hate it when someone tries to play devil's advocate on me. So I'll shut up now. :-)
J-S -- ______________________________________________________ Jean-Sebastien Guay [email protected] http://www.cm-labs.com/ http://whitestar02.webhop.org/ _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
