Please test and mark stable: =dev-ruby/tins-0.3.14 =dev-ruby/amatch-0.2.10
Why only ppc64 and x86? I see KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86". I can do both ppc and ppc64.
x86 stable
(In reply to comment #1) > Why only ppc64 and x86? I see KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86". I > can do both ppc and ppc64. Because these are the only arches that already have a stable keyword, and I think new stable keywords should be added only on user request.
(In reply to comment #3) > (In reply to comment #1) > > Why only ppc64 and x86? I see KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86". I > > can do both ppc and ppc64. > > Because these are the only arches that already have a stable keyword, and I > think new stable keywords should be added only on user request. Okay, I asked because its usually ppc that everyone wants stabilized, not ppc64. This time its the other way around. Anyhow, with FEATURES="test" we need to stabilize: =dev-ruby/test-unit-2.4.8 =dev-ruby/tins-0.3.14 =dev-ruby/amatch-0.2.10 So far test-unit-2.4.8 is fine, so I marked it stable. tins-0.3.14 fails its tests, I'll open a blocking bug, however, tins-0.4.3 passes. amatch-0.2.10 also passes but we'll wait for its dep to be fixed.
Stable ppc64. Closing as the last arch.