Shawn Walker wrote: > On 06/11/2007, James C. McPherson <James.McPherson at sun.com> wrote: ... >> If everybody in a community or project group >> insists that their pet bug is a Must Fix, then >> one..more of the group leaders must exercise >> some authority and find a way to prioritise >> those bugs. That would include marking some as >> waived or deferred - and noting the reason(s) >> why in the relevant bug/CR tracking tool. >> >> Achieving that result should most definitely >> include getting a technical justification from >> each interested party. > > I'm trying to think of any successful end-product that gets delivered > in this fashion and I'm failing to come up with examples. > > Fedora, Ubuntu, FreeBSD, etc. all seem to let the engineering or > technical teams responsible decide when something is ready for > release. > > Not a bunch of folks by votes.
Hi Shawn, I think you're responding more to Glynn's comments than mine. Getting a group leader to exercise some authority as I described is quite well sync'd to how you describe the Fedora et al process. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
