this post was submitted on 14 Oct 2025
32 points (97.1% liked)

Linux

10804 readers
542 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
 

Canonical is looking to eliminate use of its Ubuntu ISO Tracker that has been relied on the past 15+ years and in turn 30+ releases. Their ISO Tracker has grown unreliable and difficult to maintain. But without any proper solution ready, for Ubuntu 26.04 LTS the ISO Tracker may be replaced by a temporary spreadsheet and Discourse thread

top 5 comments
sorted by: hot top controversial new old
[–] onlinepersona@programming.dev 8 points 2 months ago* (last edited 2 months ago) (2 children)

Wait, they expect people to start installing Linux by creating a Google or Discord account? I have to read this article now, because the title and subtitle are hinting at this.

Ok damn, what a misleading name!

The Ubuntu ISO Tracker has long been used by the Ubuntu QA team and the community for tracking the Ubuntu Linux ISOs and their pass/fail results and other build/testing related information

It's an ISO test result tracker.

[–] fuzzzerd@programming.dev 3 points 2 months ago

I thought it was the tracker for the torrent downloads and I was like can't we just create magnet links?

Result tracking for the isos makes more sense.

[–] lengau@midwest.social 2 points 2 months ago

Discourse, not Discord. The accounts are managed through the same SSO that manages Launchpad accounts, so the devs who will use this already have an account.

[–] h54@programming.dev 5 points 2 months ago

But for now the immediate approach is to use a temporary shared spreadsheet/dashboard, Ubuntu release management maintaining a testing coordination tread on Discourse, and then to eventually have new tooling in place.

Temporary is never temporary. From a reliability and maintenance point of view, I totally get it but this temporary solution also seems terrible.

[–] logging_strict@programming.dev 3 points 2 months ago

Have been in the exact same situation. Had a code base written in PHP that needed porting to Python. i'm still porting it.

The lesson here is maybe you gotta hold on to what you have and then work on a replacement without throwing away the golden goose.

Was managing a 3,500 person network.