On Mon, Jun 22, 2009 at 1:45 PM, Pavel Machek<pavel@xxxxxx> wrote: > On Mon 2009-06-22 14:04:38, Luis R. Rodriguez wrote: >> This is losely based on previous discussions on linux-kernel [1][2][3]. >> Lets also refer people reading the stable rules to >> Documentation/development-process/. >> >> Also add the number of days it has taken between releases, >> and provide the average for the last 10 releases: 86.0 days. >> >> [1] http://marc.info/?l=linux-kernel&m=122048427801324&w=2 >> [2] http://marc.info/?l=linux-netdev&m=122048757705315&w=2 >> [3] http://marc.info/?l=linux-kernel&m=124515657407679&w=2 >> >> Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> > NAK. > >> +2.0.2: RC-SERIES RULES >> + >> +This section summarizes what kind of patches are accepted before the merge >> +window closes and after it closes. These patches are targeted for the kernel >> +prior to its final release. >> + >> +The rc-series focus should really be to address regressions. >> + >> +2.0.2.0: RC-SERIES RULES PRIOR TO THE RC1 RELEASE >> + >> +These are the types of patches that will get accepted prior to a kernel rc1 release, >> +during the merge window: >> + >> + - it must fix a regression >> + - it must fix a security hole >> + - it must fix a oops/kernel hang >> + >> +Non-intrusive bug fixes or small fixes will not be accepted. If the >> patch in > > What? Prior to rc1, new features are accepted. For maintainers yes, for developers sending to the subsystem maintainer no, at least not for that kernel release being worked on. I can try to make this a little clearer. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
