public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Cc: council@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-project] Council meeting 2024-07-21 - call for agenda items
Date: Tue, 2 Jul 2024 22:59:21 +0300	[thread overview]
Message-ID: <bb74c3a3-06c9-4c76-b9ff-b5a111b33605@gentoo.org> (raw)
In-Reply-To: <ur0cbegmn@urania.mail-host-address-is-not-set>


[-- Attachment #1.1: Type: text/plain, Size: 2992 bytes --]

On 02/07/2024 22.30, Ulrich Mueller wrote:
> ...
> 
> The agenda is still open for additional items that the council should
> discuss or vote on. For agenda items, please respond to this message
> on the gentoo-project mailing list.

I want to pass the first plan from previous thread about the Various
Gentoo Arches statuses [1], mainly the changes which aren't
controversial. I have plan for next meetings, but the next steps warrant
more talks in ML.

I think those should be separate motions, but I leave this decision to
the chairman.

a. `alpha - make profile stable`

Thanks to matoro's work, alpha dep-tree is nearly done (the latest
breakage occurred since last check, so we can say we can get a stable
tree). He is responsive for issues and pings, so I believe we can trust
this arch.

I propose we pass make the alpha profile stable (I mean profile stable,
not arch stable). We will apply the motion the moment he finishes fixing
the tree (otherwise if we wait, we risk breaking it again without noticing).


b. `ia64 - deprecate arch`

We don't believe in the possibility of continuing supporting this arch
(drop from kernel & glibc, issues with devbox). I think the normal
deprecation period of 1 year is fine here.


c. `ppc64/32ul - shorten deprecation period`

By this "arch" I mean the 32-bit userland on 64 bit kernel. None need
it, mostly broken, and all hardware that might need it has better state
(normal 64 bit userland). Currently all profiles are 17.0 and
deprecated, but I want to ask we shorter the period, since removing it
helps a lot in cleanup of ppc64 profiles mess and future keyword split.
I think 2 month from motion pass should be good enough?


d. `sparc32 - deprecate profiles`

Various reasons stated in email thread [1], no opposition. I would like
to request shorter window from 1 year, to around 3 month? For an unused
profile, I don't think we need to wait the full time?


This means all the user facing profiles of:
```
default/linux/sparc
default/linux/sparc/17.0
default/linux/sparc/17.0/desktop
default/linux/sparc/17.0/developer
default/linux/sparc/17.0/systemd/merged-usr
default/linux/sparc/23.0
default/linux/sparc/23.0/desktop
default/linux/sparc/23.0/systemd
default/linux/sparc/23.0/split-usr
default/linux/sparc/23.0/split-usr/desktop
```

e. `s390 not s390x - deprecate profiles`

I mean here the s390 not s390x variant (confusing), which is the 31 bit
variant. Various reasons stated in email thread [1], no opposition.


This means all the user facing profiles of:
```
default/linux/s390/17.0
default/linux/s390/17.0/systemd/merged-usr
default/linux/s390/23.0
default/linux/s390/23.0/systemd
default/linux/s390/23.0/split-usr
```


[1]
https://public-inbox.gentoo.org/gentoo-dev/75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org/T/

-- 
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Council, Python, pkgcore stack, QA, Arch Teams)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

           reply	other threads:[~2024-07-02 19:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <ur0cbegmn@urania.mail-host-address-is-not-set>]

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=bb74c3a3-06c9-4c76-b9ff-b5a111b33605@gentoo.org \
    --to=arthurzam@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@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