On Sun, 13 Jan 2019 at 11:09, Kevin Kofler <kevin.kofler@chello.at> wrote:
Kevin Fenzi wrote:
> When there were secondary arch koji's it took a number of people full
> time to nurse along koji shadow. Often things would land in primary,
> secondary would find a bug later and there would need to be a lot of
> coordination and back and forth before things were fixed in both places.
>
> Now all those folks can concentrate on the bugs as they happen in
> primary koji, fix them faster and everyone wins.

Well, of course it is less work for the architecture maintainers, because
they offloaded almost all the work onto us package maintainers, who have to
fix the build on architectures we don't give a darn about because they block
our entire builds. And also wait for them to complete, though sadly the main
offender there (armv7hl) has even been declared a primary architecture.

We could all get our work done much faster if the primary Koji were only
x86_64 and everything else (including ARM) were built asynchronously and
taken care of by the handful people that actually cares about the
architecture.

> If there were constant outages you might have more of a point, but this
> is the only multi-day one I can think of,

One multi-day outage is one too many.


Then your expectations are never going to be met by our Infrastructure and would be better off by designing and building your own. 

Fedora has had and will have multiple day outages. This week it was the s390. Next time it might be our storage or a cloud outage or a network problem or it might be we have to take everything down for a week in order to try and build something less likely to constantly disappoint you. However it is going to happen. Either get used to it or build the failproof alternative that is better. 

--
Stephen J Smoogen.