Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-128591

Make sure Documentation is clear on support and maintenance levels for various parts of Qt [Spike]

    XMLWordPrintable

Details

    • User Story
    • Resolution: Unresolved
    • P1: Critical
    • None
    • None
    • Documentation

    Description

      Executive summary

      The Support Terms (https://www.qt.io/terms-conditions/support-terms and new version under work here: QTPMO-2093) leave a lot of the details for what is in fact under support and maintenance to Qt Documentation. We need to make sure our Documentation is up to the task, like e.g.

      • What parts of Qt framework and tools are under LTS, and what not.
      • Other related things that should be better documented e.g. for EU CRA needs
      • How we document EoS (already separate ticket QTBUG-128581)

      Outcome of this Spike

      Outcome of this Spike is actual implementation requirements (JIRA tickets) for various needed changes.

      Desired schedule

      This Spike should be closed during 2024, and implementation requirements are identified.

      Attachments

        Issue Links

          relates to

          User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QTBUG-128581 End of life documentation improvements

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Suggestion - Public suggestions QTBUG-130508 Best practices documentation for customer maintaining Qt updateability

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Reported
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              kkohne Kai Köhne
              santtuahonen Santtu Ahonen
              Patrick Thurman Patrick Thurman
              Kai Köhne Kai Köhne
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes