On 12 Jun 2003, Arjan van de Ven wrote:
> On Thu, 2003-06-12 at 08:27, Michael Knigge wrote:
>
> > Hmmm... I don't want to tell you how you have to do your job, but this
> > is a known error and (if I followed the postings here correctly) there
> > was a fix posted. So why not include it in 2.4.22?
>
> If you wait with releases until every last and final bug is fixed,
> you'll never get a release out, because there is always SOME bug
> somewhere left, the kernel is just too big for that to not be the case.
I agree.
> It's a matter of priorities if a defect is a stopship or not, and it
> seems the bug in question isn't according to the release managers
> opinion.
And Marcello already indicated that 2.4.22 will be released only a
couple of weeks (2 months?) after 2.4.21. I think it's much more
important to have 2.4.21 final, 2.4.20 was released end november
2002, and there will be (a lot of) security fixes since then in 2.4.21.
Kind regards,
Aschwin Marsman
-- aYniK Software Solutions all You need is Knowledge Bedrijvenpark Twente 305 NL-7602 KL Almelo - the Netherlands P.O. box 134 NL-7600 AC Almelo - the Netherlands a.marsman@aYniK.com http://www.aYniK.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:33 EST