Currently in our ci we have a gnuzilla-updates, which is redundant
because we do not have a branch for it and it still points to Savannah
url. There is also a `mumi` specification, if I understand currently we
don't have a need for it too now? Can we remove both of these
specification to save compute?

I am making a new specification specifically for browsers as they have
security-updates regularly and impacts most of the users (we all
need to use browsers :P). So I wanted to ask what options should I use
for that i.e period, priority and systems.

Period is the tricky one because triggering a new build for
every force push in the pr for browsers would just waste compute.

There is already a ungoogled-chromium-updates specification, so maybe we
can just rename it?

-- 
~ Untrusem ~

In this cruel world, Kindness is punk.
https://untrusem.party

Reply via email to