Clarification on secondary architectures vs freeze exception

[Jaroslav Reznik]

Hi!
In the Alpha times, we had some disputes in terms of how to handle secondary
architecture's blockers (in that case PPC). If we should grant the freeze
exception same way as we do for all other composes that falls under 
"non-release-blocking image" or if secondary arches are a different 
beasts. As we are getting closer to Beta Change Freeze, we should clarify
it, especially as secondary architectures guys are trying to follow 
primary releases as close as possible and there are limitations on releng
side too (to pick up different versions of packages).

Personally, I think it's worth to try to apply the non-release blocking
images policy for secondary architectures. Seems like these "side" projects
are now pretty alive (often more than current non-blocking desktops!),
the community is now pretty strong, it has even marketing value and I'd
really like to see more closer relationship with secondary one day.

For cases where FE bugs could harm primary and blocking images, we can
always not to pick the fix up to the final compose (even I understand
granting FE semi-automatically could be understood as the must and 
sometimes it could be pretty tricky when touching important component
before release).

Sorry for bringing it too late, but still before today's meeting - so
at least, it could be an item for agenda :)

Thanks
Jaroslav