Non-volatile version

[tresf]

A problem we're facing downstream is we code against linuxdeployqt/releases/continuous which is continuously changing.

This is great for the casual user that needs to package on their PC from scratch, never having used linuxdeployqt before, but it's causing some issues with our CI system.

For example, recently mksquashfs has been moved internal to the linuxdeployqt AppImage, breaking any build systems which had been previously instructed to rely on it.

Are there any plans to offer some non-volatile versions so that downstream projects can maintain a baseline?

[probonopd]

The idea is that CI systems using continous automatically can benefit from the latest features and bug fixes, and that we don't have to hear about bugs that have been closed already. But I understand what you are saying. For the moment it is most pragmatic to mirror a version that is working for you, but please do watch out for changes in continuous and be aware that this is the only version we are taking bugs against.

Please understand we are a very small team and don't have the time to backport fixes to a released version.

[tresf]

Please understand we are a very small team and don't have the time to backport fixes to a released version.

Of course, this is not what's being requested here.

it is most pragmatic to mirror a version that is working for you

This seems backwards from how most other projects do things, but ok.

So is what I'm reading, that this project has absolutely no plans to offer non-volatile precompiled versions and that any project relying on this must roll their own binary release mirrors?

[TheAssassin]

Maybe we can introduce some "weekly" or "monthly" releases? If something is broken in these versions, we can always release a "minor" version a couple of days later.

[probonopd]

Volunteers welcome.

"ask not what your country can do for you — ask what you can do for your country."

John F. Kennedy

[tresf]

Volunteers welcome.

I think there's a bit of unwritten meaning in this sentence -- that (perhaps) you'd want this scripted by someone else. Simply having a project administrator upload a versioned binary release to the releases area on occasion would suffice as a stop-gap for the users that are relying on this. I would expect very few "volunteers" to qualify for this unless they were granted the appropriate access.