Re: which kernel version for etch?
* Sven Luther (sven.luther@wanadoo.fr) [060510 12:25]:
> On Wed, May 10, 2006 at 12:02:48PM +0200, Andreas Barth wrote:
> > * Sven Luther (sven.luther@wanadoo.fr) [060510 11:31]:
> > > 1) Frans is hardly competent enough to give advice for this. He is biased by
> > > his personal feud over this with me, and i believe has not a good enough
> > > oversight of the problems involved to give a good technical advice. This is my
> > > opinion, though, so feel free to ignore it.
> >
> > We need to discuss how to update the kernel for the next stable point
> > release. There is a stable release management BoF during Debconf, I'll
> > try to discuss it there. Of course, anyone can come to that BoF, and I'd
> > welcome anyone who helps us to resolve issues. (And this discussion
> > needs to happen anyways, independend of Etch.)
>
> I will not be at debconf, so i will not be able to participate in this
> discussion.
That's a pity.
> > > 2) Any discussion about this issue done during the sarge time can be thrown
> > > in the trashcan. Remember the mess that was the kernel packages in sarge,
> > > and compare it to the current situation.
> >
> > I didn't claim that Sarge and Etch are the same. However, one should and
> > could do the following: Which issues are problematic within Sarge? Could
> > that happen in Etch again? If the answer is no, I'm happy. If not, one
> > could try to fix it in time.
>
> Seems good. I listed a few points in the past, do you want that i repeat them,
> or will you find them in the archive by yourself.
Hm, best if you could send me a private mail listing these points (or
just containing pointers), so I can make sure they're picked up.
> i think that we are already in the situation where the
> corresponding teams have failed.
Perhaps I'm a bit more tolerant in that then you, but I agree that we
might come to a point where this is the case, and in that case, I'll
make sure the release team calls for a solution.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
Reply to: