> If I understand correctly, -preX releases will be for adding features and bug
> fixes and -rcX releases will be for only bug fixes.
>
> Hopefully, there won't be _any_ change from last -rc release to the -final.
That certainly seems to be the usual way to do release candidates. For
ongoing enhancement, there can either be a freeze while the -rcN process
is happening, or the next -pre fixes can go against -rc1.
Example:
2.4.20-pre5 -> 2.4.20-rc1 -> 2.4.20-rc2 -(becomes)-> 2.4.20
\
(also called)
\
\__ 2.4.21-pre0 -> 2.4.21-pre1 -> 2.4.21-pre2 -> ...
It all depends on the choice of the maintainer between holding off
addition of changes and slight increases in version numbering. Alan Cox
sort of "alternates," his releases are stable unless the ChangeLog says
otherwise. I've been using his release as "really stable" for some time,
although now I need patches which are never going to make it into the main
kernel AFAIK.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- 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/