On Sat, 17 Dec 2011 16:38:31 +0100
Pacho Ramos <email@example.com> wrote:
> El sáb, 17-12-2011 a las 16:22 +0100, "Paweł Hajdan, Jr." escribió:
> > For several mass-filed stabilization bugs I got comments why I
> > didn't cc arches like ppc.
And correctly so.
> > One problem is that I cc x86 and amd64 via "edit many bugs at once"
> > Bugzilla feature, and when filing bugs the script checks that it's
> > repoman-possible to stabilize given package on x86 and amd64.
> > Not all packages are even keyworded ~ppc, and I guess there are
> > packages that can be stabilized on x86 and amd64, but not ppc
> > because of ~ppc dependencies.
I would think you'd stabilise only packages for which a previous
version is already stable. If you focused on that, the problem of
dependencies being unstable wouldn't exist. ~arch on all ebuilds
simply means no security support, so asking to go stable means adding
that, and this changes the entire purpose of your stabilisation bugs
when you ask arch teams to go stable for the first time.
> > All of that is of course solvable with a smarter script, however I'm
> > really worried about the additional load on the "rare arches".
Um, so somebody else will have to go through the whole load of bug
reports to fix the arch teams you left out? Because your script doesn't
> > What do you think? Should I make my scripts smarter, or is it fine
> > to just cc x86 and amd64? Is anyone from non-x86-non-amd64 arch
> > teams annoyed by the queue of stabilization bugs?
I'd like you to file correct stabilisation bug reports. Which means
CCing all arches that have /previous/ ebuilds stable. We've always done
it like this.
> I am not in ppc* teams but, from my point of view, looks like they are
> understaffed and I doubt they could handle so many requests.
Same goes for all the less popular architectures.
> For mass stabilization purposes I would keep the script for amd64/x86
> only for now :-/
The only way to maintain these architectures properly is to not exclude
them in the first place. Once you start doing that, you might as well
stop supporting security, go ~arch or drop them entirely.
The only way to show there is a problem with staffing and/or the
availability of supported systems is to include these arch teams in
stabilisation bugs and then draft in more developers. In a volunteer
project, hiding the problems makes sure no one will come in and fix
The good thing about including slow arch teams is that when you've
gathered up a couple hundred or thousand bug reports, you can make a
very good case about dropping the old stable ebuilds, effectively
moving the slow arch to unstable.