Lines Matching full:release

16 The kernel developers use a loosely time-based release process, with a new
17 major kernel release happening every two or three months.  The recent
18 release history looks like this:
29 Every 5.x release is a major kernel release with new features, internal
30 API changes, and more.  A typical release can contain about 13,000
36 merging of patches for each release.  At the beginning of each development
50 time, Linus Torvalds will declare that the window is closed and release the
52 for example, the release which happens at the end of the merge window will
53 be called 5.6-rc1.  The -rc1 release is the signal that the time to
70 considered to be sufficiently stable and the final release is made.
77 	September 15	5.3 stable release
86 	November 24	5.4 stable release
90 the stable release?  The most significant metric used is the list of
98 release is made.  In the real world, this kind of perfection is hard to
100 There comes a point where delaying the final release just makes the problem
106 Once a stable release is made, its ongoing maintenance is passed off to the
107 "stable team," currently Greg Kroah-Hartman. The stable team will release
108 occasional updates to the stable release using the 5.x.y numbering scheme.
109 To be considered for an update release, a patch must (1) fix a significant
112 than one development cycle past their initial release. So, for example, the
116 	July 7		5.2 stable release
126 5.2.21 was the final stable update of the 5.2 release.
142 maintainer having the need and the time to maintain that release.  There
144 release.
200  - Stable release.  The number of users potentially affected by the patch