Kernel release

nTia89 · 2009-09-13 16:10:02

hi to all

i have a doubt :

what kind of schema follow kernel team for release it ?

Dieter@be · 2009-09-13 16:13:28

you mean arch linux kernel guys, or upstream (kernel.org) ?

sand_man · 2009-09-13 23:22:15

2.6.31 is in [testing]

nTia89 · 2009-09-14 08:57:10

yes , i mean kernel.org ...

bangkok_manouel · 2009-09-14 09:21:45

ultra basic presentation of how it works (i'm sure you'll get better replies than this one but hey, my ppd ratio sucks ATM):
after a kernel release, there's a merging period where all maintainers will ask linus to pull their work from their branches (most maintainers have their own git tree, see git.kernel.org)
then it'll be time for RC's (one RC/week) in order to track bugs and regressions until linus decides it's stable enough for a release.

there's also a -next branch which is what the kernel 2.6.x+1 will be so all new patches can be tested against each other before the real thing.

in addition, you have the -mm branch which is the experimental side of the kernel development (patches can stay there for a looooooong time e.g. reiser4 file system).

shining · 2009-09-14 09:38:58

from http://www.linuxfoundation.org/publicat … slinux.pdf

DEVELOPMENT MODEL
Linux kernel development proceeds under a loose, time-based release model, with a new major
kernel release occuring every 2–3 months. This model, which was first formalized in 2005, gets
new features into the mainline kernel and out to users with a minimum of delay. That, in turn,
speeds the pace of development and minimizes the number of external changes that distributors
need to apply. As a result, distributor kernels contain relatively few distribution-specific changes;
this leads to higher quality and fewer differences between distributions.
One significant change since the previous version of this paper is the establishment of the linux-next
tree. Linux-next serves as a staging area for the next kernel development cycle; as of this writing, 2.6.31 is in
the stabilization phase, so linux-next contains changes intended for 2.6.32. This repository gives developers a
better view of which changes are coming in the future and helps them to ensure that there will be a minimum
of integration problems when the next development cycle begins. Linux-next smooths out the development
cycle, helping it to scale to higher rates of change.
After each mainline 2.6 release, the kernel's "stable team" (currently made up of Greg Kroah-Hartman
and Chris Wright) takes up short-term maintenance, applying important fixes as they are developed. The
stable process ensures that important fixes are made available to distributors and users and that they are
incorporated into future mainline releases as well. The stable maintenance period lasts a minimum of one
development cycle and, for specific kernel releases, can go significantly longer.
This paper focuses exclusively on the mainline 2.6.x releases, to the exclusion of the stable updates. Those
updates are small, and, in any case, the design of the development process requires that fixes accepted for
-stable also be accepted into the mainline for the next major release.

nTia89 · 2009-09-14 11:59:16

shining wrote:

from http://www.linuxfoundation.org/publicat … slinux.pdf

thanks

we know how many other 2.6 kernel release remain before 2.7 tree ???

Allan · 2009-09-14 12:21:15

nTia89 wrote:

we know how many other 2.6 kernel release remain before 2.7 tree ???

Nobody knows.

shining · 2009-09-14 12:47:21

nTia89 wrote:

shining wrote:
from http://www.linuxfoundation.org/publicat … slinux.pdf
thanks
we know how many other 2.6 kernel release remain before 2.7 tree ???

If you mean a 2.7 development tree similar to 2.5, I just found a mail of Linus one year ago who said it would never happen.
http://kerneltrap.org/mailarchive/linux … 15/2497614

But this new date-based versioning mentioned there obviously did not happen either I don't know if there are any more recent discussions about it.

nTia89 · 2009-09-14 13:50:33

shining wrote:

nTia89 wrote:
shining wrote:
from http://www.linuxfoundation.org/publicat … slinux.pdf
thanks
we know how many other 2.6 kernel release remain before 2.7 tree ???
If you mean a 2.7 development tree similar to 2.5, I just found a mail of Linus one year ago who said it would never happen.
http://kerneltrap.org/mailarchive/linux … 15/2497614
But this new date-based versioning mentioned there obviously did not happen either I don't know if there are any more recent discussions about it.

OK torvalds......:/:/:/:/

Acecero · 2009-09-14 15:04:07

shining wrote:

But this new date-based versioning mentioned there obviously did not happen either I don't know if there are any more recent discussions about it.

That date-based versioning system could work, since he is not going to follow that old model, people wouldn't have to feel the tension of waiting for Linus to release the next "huge" release of the kernel after a series of 2.x or 3.x has been around for a while.

Arch Linux

#1 2009-09-13 16:10:02

Kernel release

#2 2009-09-13 16:13:28

Re: Kernel release

#3 2009-09-13 23:22:15

Re: Kernel release

#4 2009-09-14 08:57:10

Re: Kernel release

#5 2009-09-14 09:21:45

Re: Kernel release

#6 2009-09-14 09:38:58

Re: Kernel release

#7 2009-09-14 11:59:16

Re: Kernel release

#8 2009-09-14 12:21:15

Re: Kernel release

#9 2009-09-14 12:47:21

Re: Kernel release

#10 2009-09-14 13:50:33

Re: Kernel release

#11 2009-09-14 15:04:07

Re: Kernel release

Board footer