Commit 0fe8a3ce73ef31d1480e82798503948a979e8e52

Authored by Jonathan Corbet
1 parent 22c36d18c6

Various fixes to Documentation/HOWTO

Fix a number of things which have gone somewhat out-of-date over the last
few months.

Signed-off-by: Jonathan Corbet <corbet@lwn.net>

Showing 1 changed file with 19 additions and 11 deletions Side-by-side Diff

... ... @@ -249,9 +249,11 @@
249 249 release a new -rc kernel every week.
250 250 - Process continues until the kernel is considered "ready", the
251 251 process should last around 6 weeks.
252   - - A list of known regressions present in each -rc release is
253   - tracked at the following URI:
254   - http://kernelnewbies.org/known_regressions
  252 + - Known regressions in each release are periodically posted to the
  253 + linux-kernel mailing list. The goal is to reduce the length of
  254 + that list to zero before declaring the kernel to be "ready," but, in
  255 + the real world, a small number of regressions often remain at
  256 + release time.
255 257  
256 258 It is worth mentioning what Andrew Morton wrote on the linux-kernel
257 259 mailing list about kernel releases:
... ... @@ -261,7 +263,7 @@
261 263  
262 264 2.6.x.y -stable kernel tree
263 265 ---------------------------
264   -Kernels with 4 digit versions are -stable kernels. They contain
  266 +Kernels with 4-part versions are -stable kernels. They contain
265 267 relatively small and critical fixes for security problems or significant
266 268 regressions discovered in a given 2.6.x kernel.
267 269  
... ... @@ -273,7 +275,10 @@
273 275 kernel is the current stable kernel.
274 276  
275 277 2.6.x.y are maintained by the "stable" team <stable@kernel.org>, and are
276   -released almost every other week.
  278 +released as needs dictate. The normal release period is approximately
  279 +two weeks, but it can be longer if there are no pressing problems. A
  280 +security-related problem, instead, can cause a release to happen almost
  281 +instantly.
277 282  
278 283 The file Documentation/stable_kernel_rules.txt in the kernel tree
279 284 documents what kinds of changes are acceptable for the -stable tree, and
... ... @@ -298,7 +303,9 @@
298 303 inclusion in mainline.
299 304  
300 305 It is heavily encouraged that all new patches get tested in the -mm tree
301   -before they are sent to Linus for inclusion in the main kernel tree.
  306 +before they are sent to Linus for inclusion in the main kernel tree. Code
  307 +which does not make an appearance in -mm before the opening of the merge
  308 +window will prove hard to merge into the mainline.
302 309  
303 310 These kernels are not appropriate for use on systems that are supposed
304 311 to be stable and they are more risky to run than any of the other
305 312  
306 313  
... ... @@ -354,11 +361,12 @@
354 361 - SCSI, James Bottomley <James.Bottomley@SteelEye.com>
355 362 git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
356 363  
  364 + - x86, Ingo Molnar <mingo@elte.hu>
  365 + git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
  366 +
357 367 quilt trees:
358   - - USB, PCI, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de>
  368 + - USB, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de>
359 369 kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
360   - - x86-64, partly i386, Andi Kleen <ak@suse.de>
361   - ftp.firstfloor.org:/pub/ak/x86_64/quilt/
362 370  
363 371 Other kernel trees can be found listed at http://git.kernel.org/ and in
364 372 the MAINTAINERS file.
... ... @@ -392,8 +400,8 @@
392 400 bugme-new mailing list (only new bug reports are mailed here) or to the
393 401 bugme-janitor mailing list (every change in the bugzilla is mailed here)
394 402  
395   - http://lists.osdl.org/mailman/listinfo/bugme-new
396   - http://lists.osdl.org/mailman/listinfo/bugme-janitors
  403 + http://lists.linux-foundation.org/mailman/listinfo/bugme-new
  404 + http://lists.linux-foundation.org/mailman/listinfo/bugme-janitors
397 405  
398 406  
399 407