linux-kernel - Re: [PATCH] Documentation: add documentation summary for rc-series and merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090622211540.GD24236@elf.ucw.cz>
Date:	Mon, 22 Jun 2009 23:15:40 +0200
From:	Pavel Machek <pavel@....cz>
To:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Cc:	torvalds@...ux-foundation.org, Greg KH <greg@...ah.com>,
	"corbet@....net" <corbet@....net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"tshibata@...jp.nec.com" <tshibata@...jp.nec.com>
Subject: Re: [PATCH] Documentation: add documentation summary for rc-series
	and merge window

On Mon 2009-06-22 14:11:45, Luis R. Rodriguez wrote:
> On Mon, Jun 22, 2009 at 1:45 PM, Pavel Machek<pavel@....cz> 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@...eros.com>
> > 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.

Yes, it would be good if it was clearer.

If maintainer accepts non-intrusive bugfixes during merge window is
pretty much his decision, I'd say. I'd expect him to take them if he
has bandwidth available.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/