Peter Donald wrote: > On Fri, 14 Mar 2003 02:28, Rodent of Unusual Size wrote: >> Peter Donald wrote: >> > Avalons track record wrt to stability and quality control is fairly piss >> > poor except for framework/logkit/phoenix. Hell I have had my code broken >> > 4 times in the last 3 weeks let alone any extended period. >> >> 'your' code? are you referring to code in avalon, or stuff of your >> own that is based on avalon code? > > stuff based on avalon code.
aha. > Though theres enough Apache based code that is > broken .. witness James/Phoenix. that is irrelevant to my question which concerned your use of the possessive pronoun. you have clarified that you were not expressing possession of code in the asf repository; thank you for the clarification. the paragraph that follows is working from my impression that your 'my code broke' remark above has been pressed into service as a justification for some of your vetos. if that is not the case, then ignore the rest of this message. as for the breakage in your own external code: in a word, tough. that's what you get for tying it to bleeding-edge stuff. using it for your own stuff *and* being an avalon developer empowers you to work on fixing the problem. IN NO WAY does the collateral breakage of your personal code entitle you to block anyone else's work. no committer is permitted to hold up an asf project just because his/her own private work is broken by a change in cvs HEAD. as an example: if a change in the apr api broke subversion, no committer is entitled to veto or revert that change for that reason alone. i pick that particular example because there is a significant overlap between those two developer communities, and it is a scenario which could quite reasonably come up. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
