Gentoo Archives: gentoo-project

From: Rich Freeman <rich0@g.o>
To: gentoo-project <gentoo-project@l.g.o>
Subject: Re: [gentoo-project] call for agenda items -- council meeting 2017-09-10
Date: Mon, 04 Sep 2017 18:19:12
Message-Id: CAGfcS_mk65Oo1mojRDJd8KAHgvRxWHWQuycX26c+6w4gVY+Y5w@mail.gmail.com
In Reply to: Re: [gentoo-project] call for agenda items -- council meeting 2017-09-10 by "Michał Górny"
1 On Mon, Sep 4, 2017 at 2:08 PM, Michał Górny <mgorny@g.o> wrote:
2 > W dniu pon, 04.09.2017 o godzinie 12∶48 -0500, użytkownik William Hubbs
3 > napisał:
4 >> On Mon, Sep 04, 2017 at 07:36:32PM +0200, Michał Górny wrote:
5 >> > W dniu pon, 04.09.2017 o godzinie 19∶22 +0200, użytkownik David Seifert
6 >> > napisał:
7 >> > > Hi William,
8 >> > >
9 >> > > given the massive inactivity of the sparc and hppa arches, I would like
10 >> > > to request dropping their profiles to 'dev'. I would like two votes:
11 >> > >
12 >> > > 1) Should sparc be dropped to a 'dev' profile?
13 >> > >
14 >> > > 2) Should hppa be dropped to a 'dev' profile?
15 >> > >
16 >> > > I hope this can clear a lot of the STABLEREQ and KEYWORDREQ backlog
17 >> > > that is making maintenance in Gentoo cumbersome.
18 >> > >
19 >> >
20 >> > Weren't we discussing moving them to ~arch? I don't like marking
21 >> > profiles non-stable because it disables CI checks on pull requests, so
22 >> > whatever people do with those keywords, we no longer verify it.
23 >>
24 >> Moving to dev means repoman doesn't scream about things, that's the
25 >> cleaner way to go imo. Also, that means we don't have to go through the
26 >> tree and change keywords everywhere.
27 >>
28 >
29 > ...and that is a problem because...?
30 >
31
32 That is a change that is really hard to revert, while reversing the
33 stable flag would not be nearly as hard if the arch team wants to step
34 up. You don't immediately lose all the past stable testing work that
35 was done on the arch.
36
37 Long-term either approach yields the same result.
38
39 If marking the profile as dev causes some breakage for users, then
40 those users should seriously consider contributing to the arch team,
41 because they're probably the only people around who might potentially
42 do so. If not, they get to keep the pieces.
43
44 --
45 Rich

Replies