I leave the final vote to chromium to decide, which version should go stable, but I would go for ninja-1.1.0 !
Makes sense to me; we should let 1.3.3 bake a while longer. Looks like we need dev-util/re2c to be stabilized on arm before proceeding. Separate bug for that?
amd64: inherit.deprecated 1 dev-util/ninja/ninja-1.1.0.ebuild: please migrate from 'python' to 'python-r1 / python-single-r1 / python-any-r1' on line: 9 compile pass.
(In reply to Elijah "Armageddon" El Lazkani (amd64 AT) from comment #2) > amd64: > inherit.deprecated 1 > dev-util/ninja/ninja-1.1.0.ebuild: please migrate from 'python' to > 'python-r1 / python-single-r1 / python-any-r1' on line: 9 > > compile pass. The next version, ninja-1.3.3, uses python-any-r1.eclass, so that seems acceptable for now.
@chromium: Some time has passed, should we go for 1.3.3 instead?
Sounds good to me.
amd64 stable
x86 stable
alpha stable
arm stable
ppc64 stable
ping @ sparc
Closing in favor of bug 493622.