1 |
В Пн, 30/09/2013 в 00:54 +0200, Andreas K. Huettel пишет: |
2 |
> Am Sonntag, 29. September 2013, 23:41:03 schrieb hasufell: |
3 |
> > It seems this happens more frequently these days, so I'd like to |
4 |
> > remind people to check stable reverse deps before stabilizing a |
5 |
> > library, especially when this is a non-maintainer stablereq. |
6 |
> > |
7 |
> > Arch teams do not test them, so this is the business of the maintainer |
8 |
> > or the dev who requested stabilization. |
9 |
> |
10 |
> Arch testing includes testing of reverse deps. |
11 |
> If that's not the case, arch teams are not doing their job. |
12 |
|
13 |
I think it's good idea if maintainers and arch team developers will work |
14 |
in tandem and help each other by both checking reverse deps. That said |
15 |
the question here is who is in charge for stable tree stability? Stable |
16 |
tree is the arch team's primary responsibility. That is why only they |
17 |
are allowed to touch stable keywords after all. So arch team developer |
18 |
should never commit anything if at least few reverse deps were checked. |
19 |
Last but not least, I guess that average developer has lot's of things |
20 |
in package.keywords, so it's not sane to expect developer to do stable |
21 |
tree checks. |
22 |
|
23 |
-- |
24 |
Peter. |