| 1 |
On Wed, Jul 12, 2017 at 02:30:34PM +0200, Kristian Fiskerstrand wrote: |
| 2 |
> On 07/12/2017 01:59 PM, Michael Palimaka wrote: |
| 3 |
> > If it's not a stable candidate then why do you use this as an example |
| 4 |
> > against build testing-based stabilisations? If there are known issues it |
| 5 |
> > should never reach the arch teams in the first place. |
| 6 |
> |
| 7 |
> This might be the crux of things, as long as automatic stabilization is |
| 8 |
> not triggered by some set of rules (e.g 30 days in ~arch) , and still |
| 9 |
> requires manual trigger by, preferably, the maintainer there is likely |
| 10 |
> no issue. |
| 11 |
|
| 12 |
This doesn't make sense. If I have to trigger automatic stabilization, it |
| 13 |
isn't automatic any more. |
| 14 |
|
| 15 |
I think with an appropriate set of rules automatic stabilization would |
| 16 |
be fine. For example: |
| 17 |
|
| 18 |
- foo-2.0 has been in ~arch for 30 days |
| 19 |
- there are no open bugs against foo-2.0 |
| 20 |
- an older version of foo is stable |
| 21 |
- all of the dependencies of foo-2.0 are stable |
| 22 |
|
| 23 |
If those conditions are met, in theory there shouldn't be any problem |
| 24 |
with stabilizing foo-2.0. |
| 25 |
|
| 26 |
If foo-2.0 is not a stabilization candidate, there probably should be an |
| 27 |
open bug in bugzilla stating why it isn't. |
| 28 |
|
| 29 |
Thanks, |
| 30 |
|
| 31 |
William |
Archives