Re: Questions to all candidates: Release importance, release blockers, release quality
This should probably go on -devel or -project, so feel free to move the
thread.
On Fri, Mar 02, 2007 at 02:12:46AM -0800, Steve Langasek wrote:
> To state it plainly: the blocker for the etch release for the past 2 months
> or so has been the kernel. This was known, and it was stated.
>
> I don't remember seeing anyone from outside the kernel team step forward to
> tackle any of the kernel's RC bugs. This is pretty understandable -- we
> already have a large kernel team, and the package is not exactly readily
> NMUable, so trying to focus the whole project's attention on the kernel
> sounds like a classic mythical-man-month recipe for disaster, in addition to
> being a pretty huge time investment for any outside developer because of the
> kernel package's high learning curve. So what do you think should have been
> done differently in terms of release management that would have helped keep
> the release target?
One thing that's disturbed me is that I haven't seen any sort of statements
from the kernel team as to what's going on. I've heard this from the d-i
team and the release team, but no one from the kernel team has really said
anything as to what went wrong and what they're planning to do to correct
it in the future. All the other large package teams have pretty much
avoided being The Big Release Problem, and I'd personally like to know what
went wrong with the kernel so it can be avoided next time.
- David Nusinow
Reply to: