Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Special Interest Groups
  3. Qt Contribution
  4. Questions about LTS maintenance
Forum Updated to NodeBB v4.3 + New Features

Questions about LTS maintenance

Scheduled Pinned Locked Moved Unsolved Qt Contribution
2 Posts 2 Posters 49 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    malocascio
    wrote last edited by
    #1

    Hi all,

    I have some questions about how LTS releases are maintained, and I couldn't find much information in my search.

    A little while ago, I reported a bug in PySide that has since been fixed. The maintainer requested that the fix be cherry-picked into the 6.5 and 6.8 LTS releases, but the cherry-pick bot rejected both as "closed branches."

    Does that imply that LTS releases do not receive patches? Or that they only get patched under certain conditions? Or do the core Qt libraries get maintained but not the PySide bindings?

    There is an additional note that I can "contact the Releasing group to argue for inclusion," but when I emailed the address provided, I only received an automated reply that "posting to this list is restricted to subscribed members." I'd still like to advocate for its inclusion in 6.8 at least, since the patch prevents segfaults, and that is very unexpected & hard to debug for python developers. However, I'm not sure where to go with it from here.

    Are there any additional paths forward for this, or should LTS releases be considered completely frozen?

    Thanks!

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote last edited by
      #2

      Hi,

      AFAIK LTS branches do receive fixes otherwise there wouldn't be a sense to have them in the first place. At least they do in the Qt modules. For that particular case I think it might have been a glitch but I don't know how the branches are managed for Qt for Python.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved