Hello,

I have been tidying up some of the cuirass entries recently, but not
removed jobsets which I thought might still be of interest.

On Tue, Nov 17, 2026 at 06:02:24PM +0530, Untrusem wrote:
> 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 have removed mumi as it has not been triggered since 2025; probably it
has become obsolete with the move to Codeberg.

I have also removed gnuzilla-updates with its outdated specification
from Savannah, also since there was no branch anymore.

Mark, do you consult it for your updates? We could easily create a new
jobset.

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

Or we could use a generic browser updates branch.

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

Renaming is not possible in the web interface, but we could simply
delete it and create a different one. We would just need to agree on a
branch name for all browser updates. Hm, maybe there is no big need for
bikeshedding - browser-updates?

The idea would be to set it to master and add browser update commits
whenever they are around.

Andreas


Reply via email to