I'm replying to your questions from December.
yes, the secondary arches follow the same process as primary, they have
blocker bugs, etc. Also accepted blockers in secondary should be
promoted to Exceptions in primary, it would be nice to have such
"button" in the app for secondaries, but we can workaround it. It Also
means that the AcceptedBlocker/... states should be prefixed (or
suffixed) with the $arch to distinguish between primary/secondary
For a start we could have own instances for arm/aarch64, ppc and s390,
but having a multi-arch blocker app in the future would be nice I
think. And if I see correctly, you will be on the DevConf so we can
talk about the requirements and options in person there.
On Fri, 28 Nov 2014 10:44:24 +0100
Normand <normand at linux.vnet.ibm.com> wrote:
I used the blockerbugs application at
but found that
this is restricted to the primary arch releases.
Yeah, it wasn't really designed to handle releases on multiple arches.
Could it be possible to have it improved to support secondary arch
releases (ppc64, s390, ...) ?
I don't think that it could happen in time for F21 but I'm definitely
game for figuring out what changes need to happen in order for
secondary arches to use the blocker tracking app (either a new instance
or supporting multiple arches in the app).
Do the secondary arch releases use the same process as primary arch for
blockers - tracker bzs for blocker/fe, AcceptedBlocker notation etc.?