Linux wireless drivers development
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: torvalds@linux-foundation.org, Greg KH <greg@kroah.com>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"tshibata@ab.jp.nec.com" <tshibata@ab.jp.nec.com>
Subject: Re: [PATCH] Documentation: add documentation summary for rc-series and merge window
Date: Mon, 22 Jun 2009 23:15:40 +0200	[thread overview]
Message-ID: <20090622211540.GD24236@elf.ucw.cz> (raw)
In-Reply-To: <43e72e890906221411od16be51k2fc811dbf223ed9f@mail.gmail.com>

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

  reply	other threads:[~2009-06-22 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 18:04 [PATCH] Documentation: add documentation summary for rc-series and merge window Luis R. Rodriguez
2009-06-22 20:45 ` Pavel Machek
2009-06-22 21:11   ` Luis R. Rodriguez
2009-06-22 21:15     ` Pavel Machek [this message]
2009-06-22 21:18       ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090622211540.GD24236@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tshibata@ab.jp.nec.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox