1 |
On Mon, Aug 15, 2016 at 04:50:38PM +0200, Kristian Fiskerstrand wrote: |
2 |
> On 08/15/2016 04:49 PM, Kristian Fiskerstrand wrote: |
3 |
> > On 08/15/2016 04:19 PM, William Hubbs wrote: |
4 |
> >> I'm very much for this as well. Themaintainer should be able to |
5 |
> >> stabilize on all arches after the timeout. That would solve the primary |
6 |
> >> concern I have about the stable tree lagging. |
7 |
> > |
8 |
> > It depends on the context, if it is not security related or fixing a |
9 |
> > known bug, it can cause regression for stable users without much gain. |
10 |
> > |
11 |
> |
12 |
> Elaborating on this, if we're talking about maintainer stabilizing it |
13 |
> after testing it properly there is no issue, but there shouldn't be a |
14 |
> policy to auto-mark stable |
15 |
|
16 |
As a maintainer, if there is an old version of a package in stable for |
17 |
some arch and I have a stable request open for a newer version and the |
18 |
arch team doesn't respond to the stable request within a reasonable |
19 |
amount of time, I want to do one of two things: |
20 |
|
21 |
- destabilize all versions of the package on this arch. That would allow |
22 |
me to move on and take the worry about stabilizing this package off of |
23 |
the arch team in the future. or |
24 |
- if there are no blockers, stabilize the new version and deal with the |
25 |
fallout myself if there is any. |
26 |
|
27 |
If there is not an old version of the package marked stable, closing the |
28 |
stablereq and moving on is probably what I would do after a certain |
29 |
amount of time. |
30 |
|
31 |
Maintaining a viable stable tree is a team effort between the |
32 |
maintainers and the arch teams. If the arch teams are so overwhelmed |
33 |
with stable requests that they can't keep things current, the |
34 |
maintainers should be able to stabilize the newer versions and deal with |
35 |
the fallout as a last resort, or decide that they don't want their |
36 |
packages stable on those arches until the arch teams can keep up. |
37 |
|
38 |
William |