Track request kde-qt6-core22-sdk and kde-qt6-core24-sdk

store-requests
1

We are going to need to start version tracks for our content packs, starting with qt.

  • 6.7.2
  • 6.7.3
  • 6.8.0

Thanks Scarlett

2

Hi, Scarlett!

Per Process for aliases, auto-connections and tracks 2, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

I have three questions before casting my vote.

  1. What’s SNAP’s release cadence, how often is a new major version (potentially requiring a new track) released? is this documented somewhere by upstream?
  2. Is there some commitment from upstream on maintenance of old versions? e.g. is 6.7.3 still supported with security updates? will it continue to be supported now that 6.8.0 is out, and for how long?
  3. Are new versions backwards-incompatible? meaning, if I was running 6.7.2 and try to install 6.8.0, will that just work, or do I need to migrate my data/configuration, or will things break horribly?

Thanks, Alex!

3

Hi,

Looks like we need this solved first Default-provider and version tracks not supported?

That depends, if a snap depends on one version track and a user installs another version track, said snap would still use the version track it depends on right? If it tried to use the newer one, things will break for sure. I am trying to figure tracks out and see if it will solve issues such as non backward compatibility. As far as Qt support. We (kde) use the LTS release which has 18 month support cycle https://www.qt.io/product/qt6/qt-long-term-support

4

Releases https://wiki.qt.io/QtReleasing

6 months major, 3 months minor.

Scarlett

5

Hi, @scarlettmoore !

Given in consideration of all the information from you, I am still not sure that you need tracks for patch versions of Qt.

Do you have different content packs for each patch version? Could you consider adding tracks for each minor version? e.g. 6.7.x, 6.8.x, etc.

6

Right, sorry, we probably don’t need for each patch version.

I still need Default-provider and version tracks not supported? answered for the tracks to even be useful.

7

Hey, Scarlett!

I’m afraid I haven’t understood 100% the case which you described. Perhaps you should explain it with some details, maybe by providing some simplified example with links to real snaps, which may be broken.

I could create a couple of tracks for minor QT versions, please specify explicitly the snap name(s) and track names to create.

8

Lets say I build application with qt 6.7.1 and we update our content pack to qt 6.7.2, the application will instantly crash because it cannot find libraries with version 6.7.1 that the application linked to at compile time.

9

There is further discussion about the issue here Keeping the sdks at par with the runtime snaps

10

kde-qt6-core22-sdk 6.7 6.8 and kde-qt6-core24-sdk 6.7 6.8

1 Like