Gentoo Archives: gentoo-dev

From: Mart Raudsepp <leio@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] [RFC/announcement] ARM64 project / architecture team
Date: Tue, 09 Jan 2018 20:39:13
Message-Id: 1515530342.5915.3.camel@gentoo.org
In Reply to: [gentoo-dev] Re: [gentoo-dev-announce] [RFC/announcement] ARM64 project / architecture team by Aaron Bauman
1 On Tue, 2018-01-09 at 08:29 -0500, Aaron Bauman wrote:
2 >
3 > On January 8, 2018 4:32:29 AM EST, Mart Raudsepp <leio@g.o>
4 > wrote:
5 > > Hello,
6 > >
7 > > I have created a new ARM64 project[1] as an architecture team
8 > > project,
9 > > as I don't find it appropriate to handle this under the ARM project
10 > > and
11 > > all its legacy (including confusing stabilization rules, etc). It
12 > > is
13 > > also clearer that way, who is taking care of arm and who arm64,
14 > > based
15 > > on the members list.
16 > >
17 > > The current main goal is to fix up the deptree and get some arm64
18 > > profiles stable. To that effect, I'd like to ask package
19 > > maintainers to
20 > > kindly consider with arm64 as they CC architecture teams for
21 > > (re)keywording or stabilization, as if it was a stable arch.
22 > >
23 > > New members are expected to have long-term interest in the
24 > > architecture
25 > > and the work involved with that. Or responsibly removing themselves
26 > > from the project when their short-term interest fades.
27 > >
28 > >
29 > > [1]: https://wiki.gentoo.org/wiki/Project:ARM64
30 >
31 > It is great to see you have reached the point of creating the arm64
32 > project :)
33 >
34 > Would you like security to CC as well while to assist the arch as you
35 > work toward a stable profile? This would not hold/delay the security
36 > bug process until you are officially security supported, but I
37 > believe it will help achieve your goal of stabilization.
38
39 I would like arm64 to be CCed when appropriate (older version is marked
40 arm64 stable) as a courtesy on security bugs as well as STABLEREQ and
41 KEYWORDREQ bugs, and not hold back any security things for now, yes.
42
43 > If you desire to do so, security team can discuss support and our
44 > internal way forward to assist. 
45
46 I think we should reach a stable profile first, or be much closer to
47 it.
48
49
50 Mart