Re: [gentoo-dev] arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14)

[Andreas K. Huettel]

Lots of improvements implemented, see
https://wiki.gentoo.org/wiki/User:Dilfridge/GLEP:72

and the notes below for what was done...


Am Samstag, 6. Mai 2017, 18:35:08 CEST schrieb Michał Górny:
> 1. I think your example is a bit misleading -- unless I'm missing
> something, mips would be 'unstable' right now, and m68k would be
> 'testing'.

Fixed. 

> 2. I can't say I like using magical keywords like 'testing'
> and 'unstable'; they're going to be confusing long-term
> I should point out that those terms are frequently used interchangeably,
> and adding disjoint meanings to them is least misleading. Perhaps a name
> like 'transitional' for the middle state would be better?

I replaced "testing" with "mixed". So now the three values are "stable", 
"mixed", "unstable". I think that should be more clear. 

> 3. What is the use case for 'broken'? Are we ever going to use that?

I don't really know of any, so I've removed this again. 

> Rationale is 'why did I
> choose this specific solution?' -- e.g. choice of file format, keywords
> and basically answers to every useful question that has been raised.

Added, though I'm not sure it's really complete. 

> > a. whether CI should enforce correct depgraph and how,
>
> Well, my approach for this would be that CI should enforce the same things
> as
> Repoman.

Changed the wording such that it's not repoman-specific anymore. 


> > b. whether we should request stabilizing packages.
>
> We could, however, add one more column *only* for the (testing) mixed case,
> which states whether stabilization requests are required.

Implemented this, now we have a third column. That makes the specs a bit more 
complex, but it's probably worth it. And the third column will nearly always 
be empty.


-- 
Andreas K. Hüttel
dilfridge@g.o
Gentoo Linux developer (council, perl, libreoffice)