Date: Tue, 19 Nov 2002 13:11:22 -0800 (PST) From: Mike Hoskins <mike@adept.org> To: freebsd-stable@FreeBSD.ORG Subject: Re: restoring definition of -stable Message-ID: <20021119130547.E36571-100000@fubar.adept.org> In-Reply-To: <20021119104221.M19853-100000@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Nov 2002, Marc G. Fournier wrote: > Actually, major benefit to this model is that JKHs time was dedicated to > the project, so if a patch did break something, he could dedicate the time > to tracking down the person who committed (or submitted) the patch to get > it fixed, or pull it out, accordingly ... That's the release manager's job... Any software project has to have someone coordinating code freezes and deciding what fixes bugs and what destablizies code before releases. So, even with JKH gone, someone's doing that now. It probably all comes back to the fact that, again, it's one person doing a whole lot. I don't see an immediately easy way out of that. Even with eager volunteers, I wouldn't just want anyone being held responsible for release manager duties. (Presumably volunteers would need enough coding experience to say "no" when needed and backup those decissions with convincing logic.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021119130547.E36571-100000>