1 |
On Mon, Jul 10, 2017 at 4:05 PM, M. J. Everitt <m.j.everitt@×××.org> wrote: |
2 |
> |
3 |
> I dunno where you've been lately, Rich, but for most devs, would-be |
4 |
> devs, and observers .. there -are- no arch teams left .. just a few Arch |
5 |
> devs, or arch 'people' .. |
6 |
|
7 |
Obviously. |
8 |
|
9 |
I was describing how the arch team process worked when there were arch teams. |
10 |
|
11 |
The fact that most arch teams are fairly defunct is the reason that |
12 |
stable keywords have steadily been dropped. |
13 |
|
14 |
> |
15 |
> This is why stabilisation, if not for individual package maintainers on |
16 |
> amd64, has become a joke, save for Ago's efforts, and recent efforts by |
17 |
> kensington to streamline the effort for the likes of ago with his bot, |
18 |
> and one or two other arch stabilisers (who I know exist, but not by name |
19 |
> or nick). |
20 |
|
21 |
Sure. If nobody is maintaining stable keywords on an arch, then there |
22 |
shouldn't be stable keywords on that arch, unless the stable keywords |
23 |
are used for a different purpose and maintainers are free to downgrade |
24 |
them at any time. |
25 |
|
26 |
> |
27 |
> There is no, and has not been, in the time I've been involved with |
28 |
> Gentoo, any "pact" or "contract" between arch teams/devs and maintainers |
29 |
> whatsoever, anything is only ever done as a 'favour' or if someone |
30 |
> nudges the AT after the appropriate bug has been filed. |
31 |
> |
32 |
|
33 |
As a formal documented arrangement, no "pact" or "contract" has ever |
34 |
existed between arch teams and maintainers. |
35 |
|
36 |
However, this is basically the implicit basis for the system and the |
37 |
consequence of our documented policies, such as the policy that |
38 |
maintainers may not remove the highest stable version of a package. |
39 |
These policies make no sense unless arch teams are held to a standard |
40 |
of timely stabilization. |
41 |
|
42 |
There has never been a need to document such a "contract" because the |
43 |
Council has been maintaining it all along. When people complain that |
44 |
an arch team is unresponsive, the Council removes stable support for |
45 |
the arch. |
46 |
|
47 |
I'm describing reality here, not written policies. |
48 |
|
49 |
-- |
50 |
Rich |