From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] s390 has been dropped to ~s390 (testing/unstable) (resent)
Date: Tue, 6 Apr 2021 22:31:04 +0100 [thread overview]
Message-ID: <2C54ACED-FF24-434E-AA8A-D5DA12EAD97A@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
Hi,
Given I received no comments on the mailing list [0] post from 16th Feb and affirmative comments via IRC, I’ve
dropped all s390 keywords to ~s390 (testing/unstable). We’ll keep the s390 arch in addition to s390x as a subprofile
for now as this reduces the hassle of maintaining s390.
This is actually a net improvement to any users of s390 if they’re out there, as stable s390 was completely unusable
in terms of consistency given it was marked ‘exp'.
The aim is to restore s390 and s390x to being a ‘dev’ profile rather than ‘exp’ when possible, i.e. consistency
within ~s390 keywords - which does not yet exist.
I’ve started looking at what work would be needed here: https://github.com/gentoo/gentoo/pull/20270. I intend
to work on it every so often rather than it being a priority. Help welcome to file keywording bugs as indicated
by CI results in that PR!
I’ve updated all stabilisation bugs with s390@ CCed. I (ab)used NATTkA to do this so that the nuance of arch bugs
was respected (e.g. not closing bugs when s390@ wasn’t the last arch), hence the ’s390 done’ comments, which may
be slightly misleading.
TL;DR: s390 is now pure ~arch but this should be an improvement as we aim for consistency in the keywords in future. Help is
welcome. All existing stable bugs for s390 should have been updated - let me know if you find one which hasn’t been.
[0] https://archives.gentoo.org/gentoo-dev/message/69834962ec55a31908544793eb2dea05
[Originally forgot reply-to].
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
reply other threads:[~2021-04-06 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2C54ACED-FF24-434E-AA8A-D5DA12EAD97A@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox