Hi J-S -- Thanks for trying to intervene, it's appreciated.

Jean-Sébastien Guay wrote:
And Robert's under the gun (perhaps his own gun) to get a dev release out the door in a few days too. So suggesting he set up something new at this point in time was the same as him suggesting you fix the code yourself :-)

Yes, I did suggest he test the GL3 build, I figured he'd certainly want to do that given that he said he'd tag the release soon. His reply was that I should "take my attitude somewhere useful," hardly constructive or professional. Robert is free to ignore my suggestions (he has in the past), but if he tries to make it look like I'm out of line when I'm not, then I'm going to defend myself.

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.

In effect, both of you were saying "I can't fix this, I'm too busy with other things, you should fix it". And one of you had actually broken it, but the other had the errors right there in front of them. So you both could have fixed it. That's all I wanted to emphasize.

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.
   -Paul


_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to