On Fri, 2006-10-06 at 10:24 +0100, Roy Bamford wrote: > Before you can have useful reports, you need a plan to report against. > Like a target date for 2007.0 and its contents. Such a plan depends on > other projects delivering the contents in accordance with their own > plans. Like real life, these plans will have external dependencies on > $UPSTREAM, that Gentoo has little or no control over.
Please stop assuming that Release Engineering has any control over what goes on in the tree. Not only do we not have any such control, we also do not *want* any such control. A release is a *snapshot* of the Gentoo repository at a given time. We don't "plan" its contents because we *know* that we cannot make any guarantees. There's no point in saying "we're going to have Gnome 2.18" when we have zero control over it. Instead, as time nears for our planned snapshot date, we work with other teams to determine if they have things that are *close* to that snapshot date. For example, if we plan on doing a snapshot on Monday, and KDE plans on making a new version stable on Wednesday, we might hold off until Wednesday to accommodate them, but we don't pressure anyone to try to meet some arbitrary deadlines. We might also adjust the snapshot itself (as we did this release with Gnome). I'll be honest, Release Engineering work is *very* stressful. My primary goal as the lead is to try to come up with ways to make working on a release easier for the guys doing the work. I don't see how doing reporting improves their lives. After all, we put out four "reports" a year, two releases, and two meetings between the releases where we plan the next release. Anything more than that is wasteful. ;] -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
