On Tue, 2018-01-09 at 08:29 -0500, Aaron Bauman wrote: > > On January 8, 2018 4:32:29 AM EST, Mart Raudsepp <l...@gentoo.org> > wrote: > > Hello, > > > > I have created a new ARM64 project[1] as an architecture team > > project, > > as I don't find it appropriate to handle this under the ARM project > > and > > all its legacy (including confusing stabilization rules, etc). It > > is > > also clearer that way, who is taking care of arm and who arm64, > > based > > on the members list. > > > > The current main goal is to fix up the deptree and get some arm64 > > profiles stable. To that effect, I'd like to ask package > > maintainers to > > kindly consider with arm64 as they CC architecture teams for > > (re)keywording or stabilization, as if it was a stable arch. > > > > New members are expected to have long-term interest in the > > architecture > > and the work involved with that. Or responsibly removing themselves > > from the project when their short-term interest fades. > > > > > > [1]: https://wiki.gentoo.org/wiki/Project:ARM64 > > It is great to see you have reached the point of creating the arm64 > project :) > > 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.
I would like arm64 to be CCed when appropriate (older version is marked arm64 stable) as a courtesy on security bugs as well as STABLEREQ and KEYWORDREQ bugs, and not hold back any security things for now, yes. > If you desire to do so, security team can discuss support and our > internal way forward to assist. I think we should reach a stable profile first, or be much closer to it. Mart
