On Mon, 15 Aug 2016 15:03:08 +0200 Kristian Fiskerstrand <k...@gentoo.org> wrote:
> Could you please elaborate a bit? In particular from perspective of (i) > integration into current workflow, (ii) complexity in application > maintenance/hosting (iii) cost/benefit considerations Biggest irritation is that "bugs track concepts" but "arches track arches" so "One bug many arches" -> Anarchy. A competing tool I'd imagine would possibly automatically designate packages that are stable /candidates/ and keywording /candidates/ without any manual interaction. ie: It would essentially double down on the "Batch stabilization/keywording" concept and represent that concept portage wide, but only in an informal sense. Then you could basically filter it by views on a per-arch basis to see what needs doing on a given arch, and mark "candidates" as "needed to be done" and tree based recursive integrity checking would be part of the workflow. So you'd see "X is stable candidate for x86" You'd click "x86" and it would produce a list of the subgraph that also needs stabilizing to satisfy, and you'd give it a once over, click "Ok" and that package and its dependencies are now "marked for stabilization on x86". Then AT teams could come along and simply use a different view that shows only stabilization requests for their arch, and do them in bulk, or piecemeal, at their own discretion. unkeyworded -> keywording candidate -> keywording request -> keyworded keyworded -> stable candidate -> stable request -> stable But these are just ideas ;)
pgpiqjSuE1dad.pgp
Description: OpenPGP digital signature
