1 |
On 16/06/16 13:04, Michał Górny wrote: |
2 |
> On Wed, 15 Jun 2016 21:11:30 +0200 |
3 |
> Michał Górny <mgorny@g.o> wrote: |
4 |
> |
5 |
>> Right now we have the following components: |
6 |
>> |
7 |
>> - Applications, |
8 |
>> - baselayout, |
9 |
>> - Core system, |
10 |
>> - Development, |
11 |
>> - Eclasses and Profiles, |
12 |
>> - Games, |
13 |
>> - GCC Porting, |
14 |
>> - GNOME, |
15 |
>> - Hardened, |
16 |
>> - Java, |
17 |
>> - KDE, |
18 |
>> - Keywording & Stabilization, |
19 |
>> - Library, |
20 |
>> - New packages ('New ebuilds' previously), |
21 |
>> - Printing, |
22 |
>> - SELinux, |
23 |
>> - Server, |
24 |
>> - Unspecified. |
25 |
> Revision two: |
26 |
> |
27 |
> - Current packages [bug-wranglers@], |
28 |
> - Eclasses [bug-wranglers@], |
29 |
> - Hardened [hardened@], |
30 |
> - New packages [bug-wranglers@], |
31 |
> - Overlays [overlays@], |
32 |
> - Profiles [bug-wranglers@], |
33 |
> - SELinux [selinux@]. |
34 |
> |
35 |
> Major changes: |
36 |
> |
37 |
> 1. collapsed all category-like components into a single 'Current |
38 |
> packages' that is the default component for pretty much every bug |
39 |
> related to 'standard' configurations of Gentoo Linux -- making it easy |
40 |
> to choose the correct one and ensuring everything goes through |
41 |
> bug-wranglers; |
42 |
> |
43 |
> 2. split 'eclasses & profiles' into two separate categories -- mainly |
44 |
> intended for developer use; |
45 |
> |
46 |
> 3. left 'Hardened' and 'SELinux' (also the whole separate Gentoo/Alt |
47 |
> product) as the non-standard system configurations that desire staging |
48 |
> the bugs through respective teams, |
49 |
> |
50 |
> 4. left 'New packages' as-is, as category for requesting addition |
51 |
> of packages not yet in Gentoo, |
52 |
> |
53 |
> 5. added 'Overlays' component for bugs filed against packages |
54 |
> in third-party repositories (right now some of them got filed pretty |
55 |
> randomly, and having them in Infra->Overlays is kinda wrong), |
56 |
> |
57 |
> 6. removed 'Keywording & stabilization'. As pointed out, those can be |
58 |
> handled via keywords and we already do stabilizations in other places |
59 |
> (e.g. security bugs). |
60 |
> |
61 |
> Your thoughts about this one? |
62 |
> |
63 |
Looks good. +1 here. |