Date: Wed, 21 May 1997 09:45:43 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Bruce Evans <bde@zeta.org.au> Cc: asami@vader.cs.berkeley.edu, current@FreeBSD.ORG, jdp@polstra.com, rob@ideal.net.au Subject: Re: IPDIVERT broken? Message-ID: <2567.864233143@time.cdrom.com> In-Reply-To: Your message of "Thu, 22 May 1997 02:16:07 %2B1000." <199705211616.CAA31817@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> Developers should help make the changes. For ipdivert and nonstandard > network protocols they were given several weeks notice but apparently > didn't do anything until after the changes were committed. If you said: "Developers should *try* to help make the changes" then I'd have no argument at all, and it's certainly not unrealistic to hope that general team-spiritedness would be invoked if person A came along and said "I've got this big, hairy change to make and it's really a good thing in the long term but I kinda need some help, guys. Please?" However, I'm not talking about the nice-to-have scenario, I'm talking about formulating an effective policy which allows us to handle the failure cases like this and I still think that *ultimate* responsibility should fall upon the changer, not a more nebulous conglomeration of hoped-for favors and group effort. That way lies madness and a broken source tree during the times when said developers are on 6 week treks across the Himalayas or are simply too busy with new projects of their own to go clean up after someone else in code they downed tools on months previously. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2567.864233143>