| 1 |
On January 8, 2018 4:32:29 AM EST, Mart Raudsepp <leio@g.o> wrote: |
| 2 |
>Hello, |
| 3 |
> |
| 4 |
>I have created a new ARM64 project[1] as an architecture team project, |
| 5 |
>as I don't find it appropriate to handle this under the ARM project and |
| 6 |
>all its legacy (including confusing stabilization rules, etc). It is |
| 7 |
>also clearer that way, who is taking care of arm and who arm64, based |
| 8 |
>on the members list. |
| 9 |
> |
| 10 |
>The current main goal is to fix up the deptree and get some arm64 |
| 11 |
>profiles stable. To that effect, I'd like to ask package maintainers to |
| 12 |
>kindly consider with arm64 as they CC architecture teams for |
| 13 |
>(re)keywording or stabilization, as if it was a stable arch. |
| 14 |
> |
| 15 |
>New members are expected to have long-term interest in the architecture |
| 16 |
>and the work involved with that. Or responsibly removing themselves |
| 17 |
>from the project when their short-term interest fades. |
| 18 |
> |
| 19 |
> |
| 20 |
>[1]: https://wiki.gentoo.org/wiki/Project:ARM64 |
| 21 |
|
| 22 |
It is great to see you have reached the point of creating the arm64 project :) |
| 23 |
|
| 24 |
Would you like security to CC as well while to assist the arch as you work toward a stable profile? This would not hold/delay the security bug process until you are officially security supported, but I believe it will help achieve your goal of stabilization. |
| 25 |
|
| 26 |
If you desire to do so, security team can discuss support and our internal way forward to assist. |
| 27 |
|
| 28 |
-Aaron |
| 29 |
|
| 30 |
-- |
| 31 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives