1 |
On Tuesday, August 1, 2017 6:35:35 AM EDT Kristian Fiskerstrand wrote: |
2 |
> On 08/01/2017 01:43 AM, Benda Xu wrote: |
3 |
> > Is it feasible to reduce the workload by only stablizing the longterm |
4 |
> > supported kernels? |
5 |
> |
6 |
> On 08/01/2017 12:30 AM, Rich Freeman wrote: |
7 |
> > I'd suggest taking it further and allowing auto-stabilization of all |
8 |
> > point releases whether they're security releases or not. |
9 |
> |
10 |
> Both of these are also in line with what has previously been [discussed |
11 |
> in wg-stable]: |
12 |
> --<---------------------------------------------------->-- |
13 |
> \subsection{Kernel} |
14 |
> There should be kernel packages in stable visibility available to end |
15 |
> users for \pkg{sys-kernel/gentoo-sources} and other kernel variants |
16 |
> referenced in the installation instructions of the handbook, in order to |
17 |
> ease the configuration for new users. |
18 |
> |
19 |
> For Kernel stabilisation it is not possible for an arch tester to test |
20 |
> all possible configuration and hardware combinations. Other kernel |
21 |
> variants, that are expected for more advanced users to begin with, |
22 |
> likely does not make sense to stabilise given there the lack of |
23 |
> stability guarantees. Restricing the number of stabilised kernels hence |
24 |
> aids in reducing arch tester workload. |
25 |
> |
26 |
> As discussed previously\cite{kernel01,kernel02} a consistent |
27 |
> stabilisation policy on kernels is also important in order to ensure |
28 |
> that the latest point release is available to end-users in order to |
29 |
> ensure that security- and bugfixes are offered. In the experience of the |
30 |
> WG the kernel upstream has a strict policy on maintaining backwards |
31 |
> compatibility and not breaking userspace which has been proven over time. |
32 |
> |
33 |
> As such it makes sense to |
34 |
> \begin{itemize} |
35 |
> \item Stabilise Long Term Stable (LTS) branches once they have been |
36 |
> determined to be so and tested downstream |
37 |
> \item Have an automatic policy of stabilising new point releases |
38 |
> within the LTS |
39 |
> \item non-LTS branches should not be stabilised |
40 |
> \end{itemize} |
41 |
> |
42 |
> --<---------------------------------------------------->-- |
43 |
> |
44 |
> References: |
45 |
> [discussed in wg-stable] |
46 |
> https://download.sumptuouscapital.com/gentoo/wg-stable/main.pdf |
47 |
|
48 |
So will the council consider ratifying the WG stable suggestions for kernel |
49 |
releases? |
50 |
|
51 |
-Aaron |