On 11/17/26 13:32, Untrusem wrote:

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).

Thanks. If we want to do security updates for browsers through pull requests, then we should have a high priority CI specification for those.

E.g. the icecat updates are often pushed directly to master to ensure security updates reach the users as quickly as possible, because the CI currently takes too long (gnuzilla-ubdates has priority 9).

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

Would it? I think a build on every push would be fine, especially for browsers, because they usually only require one or two commits.

And people will usually push commits they have tested locally. (Or alternatively people might push commits they want to build on the shared infrastructure because they cannot build it on their own machines.)

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



Reply via email to