>
> => Keep it simple: Stable should mean the same across all architectures
OK, this is a definite statement, so stable remains stable, and we introduce no
additionally different status.
I'd recommend that you drop the "security-supported arches" list from the
security team web page too.
--
Hi,
regarding "security supported architectures" a few words from security
project:
We don't like the differentiation. And in practice, it doesn't even
matter nor does it work:
In theory, "security supported architectures" would allow us to ignore
bugs only affecting specific architectures. But
On Fri, 2020-04-10 at 13:37 +0300, Andreas K. Hüttel wrote:
> Am Freitag, 10. April 2020, 09:58:37 EEST schrieb Michał Górny:
> > 1. 'Broken' status was removed, as it is redundant to profile status.
> >
> > 2. State names were changed from 'testing' and 'unstable' to 'degraded'
> >(broken
Am Freitag, 10. April 2020, 09:58:37 EEST schrieb Michał Górny:
>
> 1. 'Broken' status was removed, as it is redundant to profile status.
>
> 2. State names were changed from 'testing' and 'unstable' to 'degraded'
>(broken stable tree) and 'testing' (pure ~arch) to avoid confusion.
>
Back
Hi,
I've just found another use case for arches.desc, so I'd like to revive
dilfridge's GLEP. I tried to keep the changes to minimum, while
addressing earlier concerns.
Besides wording changes and clarifications, the following significant
changes were made:
1. 'Broken' status was removed, as
