blob: af4d67391c924248a8226e263e442dcac56be1be (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
\summary{2011}{2}{1}
Agenda call: \agoref{gentoo-project}{63cc1e0f9165834ad109481ca2ed02ab}
Agenda announcement: ---
\agendaitem{Slacker arches}
\index{arches!slacking}
After a brief discussion about the mailing list thread, Jorge raised a few
concerns about the proposed policy\footnote{This most likely refers to
\agoref{gentoo-dev}{1e5165eab52d33da32f40e622b66ada4}.} increasing arch teams
work and not addressing the issue of lacking hardware. It was decided that
\dev{scarabeus} will write a proposal based on the mailing list thread
and that \dev{jmbvicetto} will try to talk to the arch teams and trustees to see
if there is or not a hardware issue and if so will try to address it.
\agendaitem{EAPI 4}
\index{EAPI!4!approval}\index{EAPI!usage when bumping}\index{upgrade path}
The council already approved and published the use of EAPI 4 for testing
ebuilds in the tree, see \agoref{gentoo-dev}{32b31cd9601ab6859269e2edfa86c9d7}.
While mentioning this point, \dev{scarabeus} recalled his question about changing
policy to have developers use the latest EAPI whenever possible, which
lead to a long discussion about deprecating EAPI versions and upgrade
paths, to be continued on the mailing lists.
\agendaitem{GLEP 48}
\index{GLEP!48}\index{project!qa}
There was a very long discussion about ``authority'' and ``powers'' and whether
QA should or not have be able to suspend developer's commit privileges.
No consensus was reached and as proposed in the agenda, the GLEP was sent
back to be updated with current requests and for further discussion on mailing
lists.
\agendaitem{Open floor}
No issues were brought forward to the council.
|
GitWeb
