Hi, we'd like to make Enginio part of the release. qtenginio behaves like any other module. What are the criteria for it to become part of a regular release?
(I can do the merge myself, but I wouldn't mind if it was part of the big merge etc.) Greetings, Frederik Fredag 3. januar 2014 13.35.30 skrev Paaso Matti: > Hi, > > We are about to start the "Qt 5.2.1" release as agreed in [1], which means > that: > > - We plan to do a fast-forward merge from 'stable' into 'release' branch > on Jan 13th. > > - After Jan 13th any changes that are required for 5.2.1 need to be > pushed to the 'release' branch. So if your changes are not in by that > day, please wait until the merge is done and re-target them to the > 'release' branch. > > The repositories that will be part of the Qt 5.2.1 release merge are: > > - qt5 > - qtactiveqt > - qtandroidextras > - qtbase > - qtconnectivity > - qtdeclarative > - qtdoc > - qtgraphicaleffects > - qtimageformats > - qtlocation > - qtmacextras > - qtmultimedia > - qtquick1 > - qtquickcontrols > - qtscript > - qtsensors > - qtserialport > - qtsvg > - qttools > - qttranslations > - qtwebkit > - qtwebkit-examples > - qtwinextras > - qtxmlpatterns > - qtx11extras > > [1]: > http://lists.qt-project.org/pipermail/releasing/2013-December/001557.html > > Cheers, > -- > Matti Paaso > SW Engineer - Digia, Qt -- Best regards, Frederik Gladhorn Senior Software Engineer - Digia, Qt Visit us on: http://qt.digia.com _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
