Lines Matching refs:release

13 The kernel developers use a loosely time-based release process, with a new
14 major kernel release happening every two or three months.  The recent
15 release history looks like this:
24 Every 2.6.x release is a major kernel release with new features, internal
25 API changes, and more.  A typical 2.6 release can contain nearly 10,000
31 merging of patches for each release.  At the beginning of each development
45 time, Linus Torvalds will declare that the window is closed and release the
47 for example, the release which happens at the end of the merge window will
48 be called 2.6.40-rc1.  The -rc1 release is the signal that the time to
65 considered to be sufficiently stable and the final 2.6.x release is made.
71 	January 4	2.6.37 stable release
80 	March 14	2.6.38 stable release
83 the stable release?  The most significant metric used is the list of
91 release is made.  In the real world, this kind of perfection is hard to
93 There comes a point where delaying the final release just makes the problem
99 Once a stable release is made, its ongoing maintenance is passed off to the
101 will release occasional updates to the stable release using the 2.6.x.y
102 numbering scheme.  To be considered for an update release, a patch must (1)
105 a little more than one development cycle past their initial release.  So,
108 	October 10	2.6.36 stable release
114 2.6.36.4 was the final stable update for the 2.6.36 release.
125 maintainer having the need and the time to maintain that release.  There
127 release.
182  - Stable release.  The number of users potentially affected by the patch