1 |
Tobias Scherbaum wrote: |
2 |
> Thilo Bangert wrote: |
3 |
>>>> Now what do people think about extending metadata.xml so that you |
4 |
>>>> could have these |
5 |
>>>> bugs filed automatically when there are no open bugs? Something like |
6 |
>>>> a <auto-stable-request enabled="true"/> |
7 |
>>>> element with the DTD setting the default as true and you could just |
8 |
>>>> use a <auto-stable-request /> shorthand. |
9 |
>> good idea. |
10 |
> |
11 |
> +1 |
12 |
> |
13 |
>>> I'm all for it. It would need to take version restrictions -- for |
14 |
>>> example, I may be willing to have xorg-server 1.5.x go stable but not |
15 |
>>> 1.4.x. |
16 |
>> perhaps auto-stable should be the default (not needing the tag), only |
17 |
>> allowing things to be masked from it. |
18 |
> |
19 |
> I'm not sure if it's really useful to have this as a default - for |
20 |
> example i keep nagios-3 packages intentionally ~arch for now. Tagging |
21 |
> them as "not ready for stabilization yet" would introduce something |
22 |
> between ~arch masked and package.mask - i don't think that's worth the |
23 |
> effort. |
24 |
> |
25 |
> From both a maintainers and arch-developers view: I'd like to see |
26 |
> automatically generated stable requests, but I'd leave it up to the |
27 |
> maintainer/herd/team to add architectures after a quick review (also if |
28 |
> there's a auto-stable-request tag set in metadata!). |
29 |
> |
30 |
> Tobias |
31 |
|
32 |
So we would have <auto-stable-request add-arches="false" /> with it |
33 |
defaulting to true. |
34 |
|
35 |
Regards, |
36 |
Petteri |