On Monday 05 September 2005 05:11, Stuart Herbert wrote: > I'd be more worried about the impact on users. From a user's point of > view, x86 is a fast-moving arch, where you can normally find an up to > date package, and where most of the major packages are actively and well > maintained by the package maintainers. The introduction of the x86 arch > team will, at some point, turn the x86 arch team into a bottleneck (just > like all the other arch teams already are), and the experience for our > users will change. Our challenge as a project is make sure that the > benefits of the x86 team outweigh the negatives in the right places, so > that we don't lose our users in the process.
Somewhere in the previous thread, I read the (seemingly sarcastic) suggestion that all non-arch devs start working in overlays. This would seem to be a very good idea if the overlays could be made easily available via gensync. Having general ebuild devs work in overlays (perhaps shared overlays per herd?) rather the main tree would seem to be better for at least two reasons: * "Proper" arch testing by arch-devs (Dunno if this is valid, but other's are bringing it up in this thread, so... ;) * Users would select what areas in which the pace should be fast. This has the added benefit that mix of arch/~arch bugs that slip through a all ~arch system would be picked up a lot more. -- Jason Stubbs
pgpUIGF7N5UuK.pgp
Description: PGP signature
