1 |
On Thu, Aug 22, 2013 at 1:39 AM, Ben de Groot <yngwin@g.o> wrote: |
2 |
> On 22 August 2013 01:19, Matt Turner <mattst88@g.o> wrote: |
3 |
>> On Wed, Aug 21, 2013 at 8:50 AM, Markos Chandras <hwoarang@g.o> wrote: |
4 |
>>> Is there an alternative? afaik a profile can be either stable,dev or |
5 |
>>> exp. I can't see how we can implement something between |
6 |
>>> stable and dev. And what would that represent? It may or may not be |
7 |
>>> stable? If this is the case, then I believe ~arch is more preferred. |
8 |
>> |
9 |
>> I haven't read much into it, but Fedora has a concept of "Secondary |
10 |
>> Architectures." I think it would make sense if we could keep stable |
11 |
>> keywords for them, but not prevent maintainers from needing to wait on |
12 |
>> them to stabilize other packages. |
13 |
> |
14 |
> I don't see how that would work. You can't remove older versions |
15 |
> unless a newer one is stabilized, or you'd break the tree. |
16 |
|
17 |
Sort-of. You'd break it in that users would have to accept ~arch to |
18 |
keep that package, or remove it. It is really no different than |
19 |
dropping stable keywords which forces them to do the same thing, |
20 |
except that you're doing it one package at a time. |
21 |
|
22 |
You could impose a time limit to respond to the STABLEREQ prior to |
23 |
removal (30-60 days or something). |
24 |
|
25 |
I think the result of a policy like this would be that stable keywords |
26 |
would get dropped on most peripheral packages, but system packages |
27 |
might still keep them. That might actually be the right balance - if |
28 |
the arch teams focus on just system or other important packages they |
29 |
might be able to find the time to keep up rather than trying to boil |
30 |
the ocean. |
31 |
|
32 |
Rich |