Gentoo Archives: gentoo-project

From: Brian Evans <grknight@g.o>
To: gentoo-project@l.g.o
Subject: [gentoo-project] Re: [gentoo-dev-announce] Call for agenda items - Council meeting 2018-01-14
Date: Tue, 09 Jan 2018 02:03:31
Message-Id: f26d5796-bb6e-23d6-e92d-6b25bd7be362@gentoo.org
In Reply to: [gentoo-project] Call for agenda items - Council meeting 2018-01-14 by Ulrich Mueller
On 1/2/2018 8:35 AM, Ulrich Mueller 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). > > The agenda for the meeting will be sent out on Sunday 2018-01-07. > > Please reply to the gentoo-project list. > > Ulrich >
I feel the council should discuss the current disarray that are the profiles. How new profiles are communicated to users is only causing confusion. There are currently two GLEP-42 news items that users see. If they haven't updated in a few months, they will see the 17.1 news item first, on amd64, because of the 'Display-If-Installed: >=sys-devel/gcc-6.4.0' restriction of the 17.0 profile news item. While at the same time, the 13.0 profile is marked as deprecated and portage complains. Until just recently, the 17.1 profile looked like what users had to migrate to on the most common arch, amd64. We need a set of standard procedures and recommendations to properly navigate through this swamp of a transition. Should there be a (better) mechanism on profile changes? Thanks, Brian

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies