From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org, mgorny@gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2019-05-12
Date: Sun, 5 May 2019 17:37:08 -0500 [thread overview]
Message-ID: <20190505223708.GA307@linux1.home> (raw)
In-Reply-To: <20190505182137.GA16389@linux1.home>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
On Sun, May 05, 2019 at 01:21:37PM -0500, William Hubbs wrote:
> On Sun, May 05, 2019 at 08:51:10AM +0200, Michał Górny wrote:
> > On Mon, 2019-04-29 at 00:42 +0200, Thomas Deutschmann wrote:
> > > In two weeks from now, the council will meet again. This is the time
> > > to raise and prepare items that the council should put on the agenda
> > > to discuss or vote on.
> > >
> > > Please respond to this message with agenda items. Do not hesitate to
> > > repeat your agenda item here with a pointer if you previously
> > > suggested one (since the last meeting).
> > >
> >
> > I would like to request the Council to vote on making 17.1 profiles
> > stable. The profiles were present for a 1.5 yr now, and are in dev for
> > half a year. The most important obstacles on the course to migration
> > have been removed, the remaining bugs being either 'cleanup to be done
> > once we switch' or dead packages.
> >
> > If large number of stable profiles is the problem, I'd suggest marking
> > 17.0 dev simultaneously. This shouldn't cause any major problems since
> > breakage relating to one category of profiles and not the other is
> > rather unlikely, and responsible devs use 'repoman full -d' anyway.
>
> I don't know what happened on the ppc* side, it looks like they do not
> have 17.1 profiles any more. The only arch this will affect is amd64.
>
> I would suggest starting work on deprecating the older profiles instead
> of marking them dev.
>
> I think it should be time for the 13.0 profiles to go, and maybe the
> 17.0 profiles for amd64 once the 17.1 profiles are stable.
After looking at this a bit further, the 13.0 profiles should definitely
be going away [1].
And I still think we should deprecate the 17.0 profiles for amd64.
Thanks,
William
[1] https://bugs.gentoo.org/672960
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2019-05-05 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 22:42 [gentoo-project] Call for agenda items - Council meeting 2019-05-12 Thomas Deutschmann
2019-04-29 1:46 ` Rich Freeman
2019-04-29 15:10 ` Matthew Thode
2019-04-29 15:37 ` Rich Freeman
2019-04-29 5:31 ` [gentoo-project] Re: [gentoo-dev-announce] " Michał Górny
2019-04-29 7:37 ` Ulrich Mueller
2019-04-29 12:10 ` Michał Górny
2019-04-29 17:17 ` [gentoo-project] " Matthias Maier
2019-04-29 17:28 ` Alec Warner
2019-04-29 17:32 ` Matthias Maier
2019-05-04 14:49 ` Ulrich Mueller
2019-05-05 6:51 ` Michał Górny
2019-05-05 18:21 ` William Hubbs
2019-05-05 22:37 ` William Hubbs [this message]
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=20190505223708.GA307@linux1.home \
--to=williamh@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=mgorny@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