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

Document measures in place making "Year 2038" not a problem for Qt

    XMLWordPrintable

Details

    • Task
    • Resolution: Incomplete
    • P2: Important
    • 6.8
    • 6.8
    • Core: Date/Time
    • None
    • All
    • Foundation PM Prioritized

    Description

      As the origin of this issue, QTBUG-124012, shows, "Year 2038" will not be a problem with Qt if API are used right. I would like to see this reflected in the docs. This was mentioned in the comments before, but a separate task would probably be more helpful. 

      As a result, I would like to see a note on the docs which would also mention this "problem" explicitly so that a user can find the related page quickly

      Attachments

        Issue Links

          clones

          Task - A task that needs to be done. QTBUG-124012 Analyse an impact of the "Year 2038" problem

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          resulted from

          Task - A task that needs to be done. QTBUG-124012 Analyse an impact of the "Year 2038" problem

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              vminenko Vladimir Minenko
              vminenko Vladimir Minenko
              Vladimir Minenko Vladimir Minenko
              Alex Blasche Alex Blasche
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes