| 1 |
On 1/2/2018 8:35 AM, Ulrich Mueller wrote: |
| 2 |
> In two weeks from now, the council will meet again. This is the time |
| 3 |
> to raise and prepare items that the council should put on the agenda |
| 4 |
> to discuss or vote on. |
| 5 |
> |
| 6 |
> Please respond to this message with agenda items. Do not hesitate to |
| 7 |
> repeat your agenda item here with a pointer if you previously |
| 8 |
> suggested one (since the last meeting). |
| 9 |
> |
| 10 |
> The agenda for the meeting will be sent out on Sunday 2018-01-07. |
| 11 |
> |
| 12 |
> Please reply to the gentoo-project list. |
| 13 |
> |
| 14 |
> Ulrich |
| 15 |
> |
| 16 |
|
| 17 |
I feel the council should discuss the current disarray that are the |
| 18 |
profiles. |
| 19 |
|
| 20 |
How new profiles are communicated to users is only causing confusion. |
| 21 |
There are currently two GLEP-42 news items that users see. If they |
| 22 |
haven't updated in a few months, they will see the 17.1 news item first, |
| 23 |
on amd64, because of the 'Display-If-Installed: >=sys-devel/gcc-6.4.0' |
| 24 |
restriction of the 17.0 profile news item. |
| 25 |
While at the same time, the 13.0 profile is marked as deprecated and |
| 26 |
portage complains. |
| 27 |
Until just recently, the 17.1 profile looked like what users had to |
| 28 |
migrate to on the most common arch, amd64. |
| 29 |
|
| 30 |
We need a set of standard procedures and recommendations to properly |
| 31 |
navigate through this swamp of a transition. |
| 32 |
|
| 33 |
Should there be a (better) mechanism on profile changes? |
| 34 |
|
| 35 |
|
| 36 |
Thanks, |
| 37 |
|
| 38 |
Brian |
Archives