Use local daily updated Debian for release pipeline

[LittleHuba]

No description provided.

[LittleHuba]

/azp run create-installers

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[LittleHuba]

The requested installers were generated successfully. The installers are available at:

• Windows
• macOS
• Debian
• Ubuntu 20.04
• Ubuntu 22.04

Please be aware that these links are only valid for a limited time (~30 days).

[Febbe]

I would do this, after the release of 1.3.x. @bhennion, @rolandlo, is there something we should add in 1.x / 1.3.x before we start developing 2.0?

[Febbe]

lgtm

[rolandlo]

Thanks @LittleHuba for taking the time.

[bhennion]

I would do this, after the release of 1.3.x. @bhennion, @rolandlo, is there something we should add in 1.x / 1.3.x before we start developing 2.0?

Of the PR/issues tagged with the milestone, I'd say that #5528 should be merged first. For the rest, new features can wait 2.0 and bug fixes could go in 1.3.1.

[rolandlo]

I would do this, after the release of 1.3.x. @bhennion, @rolandlo, is there something we should add in 1.x / 1.3.x before we start developing 2.0?

Wouldn't it be better if @bhennion's preparation for Gtk4 PR's like #5602 and #5644 were part of 1.3.0?

For 1.2.4 I'd like to look into #5635 (which happens on Sonoma, but not on Catalina), since it would be better to fix this dark theme issue fully rather than in two steps. We should also wait for #5638 I think.

For 1.3.0 we may also need to decide what to do with #5273.

Edit: update after #5635 was fixed.

[Febbe]

Wouldn't it be better if @bhennion's preparation for Gtk4 PR's like #5602 and #5644 were part of 1.3.0?

Yes, the preparations should go into 1.X.
Features -> 1.3
Bugfixes -> 1.2.x

new features can wait 2.0

I am not sure here, many features will then wait a long time until they land in a stable release.
It depends on if they are features for us devs or features for the user.

E.g. rotating assets. It's a feature desired by many people. We just didn't add it, because it would've required a change for the file format.
But when we wait for the new file format that could again block 2.0 for a long time.