Uploaded image for project: 'Qt 3D Studio'
  1. Qt 3D Studio
  2. QT3DS-1870 Releasing of Qt 3D Studio 2.0.1
  3. QT3DS-1872

Make Qt 3D Studio Runtime 2.0.1 preview config

    XMLWordPrintable

Details

    Description

      Using content from qt3dstudio/qt3d-runtime/2.0.1 (that are configured to build against Qt 5.11.1 final release content) to create preview config to make installers available on staging servers for Qt 3D Studio 2.0.1 and for Qt 3D Studio 2.0.1 Runtime under "Preview" section of the online installer.

      Attachments

        Issue Links

          depends on

          Technical task - A technical task. QT3DS-1871 Create release branches for Qt 3D Studio 2.0.1

          • 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

          Technical task - A technical task. QT3DS-1930 Update the runtime MODULE_VERSION in 2.0.1 branch

          • 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

          Technical task - A technical task. QT3DS-1931 Update the editor MODULE_VERSION in 2.0.1 branch

          • 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

          Activity

            People

              ankokko Antti Kokko
              pakerane Pasi Keränen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: