[Development] How to release critical fixes?

Turunen Tuukka Tuukka.Turunen at digia.com
Fri Oct 5 17:21:09 CEST 2012

The new release process already addresses this. After we have it in place, it will be straightforward. It is ok to discuss, but very much has already been planned and agreed. We just need to take it into use.

However the fact that Qt is a cross-platform toolkit still remains an item we need to consider. So it will still require a lot of verification work even with the new process.

But it is anyway much better than the current one where there is no release branch to use.




Rafael Roquetto kirjoitti 5.10.2012 17:33:

Hello all,

Following the discussion concerning 4.8.3-1 vs 4.8.4, I think an important
gap on the workflow has been exposed: how to release critical patches? I am
not sure if this makes sense, since I am entirely not acquitanted to the
entire release process, but would anyone have any suggestion or comments on
how we could issue these exceptional releases that should only include highly
critical fixes (i.e. the SSL one)? Feedback?

** Qt Developer Conference: http://qtconference.kdab.com/ **

Rafael Roquetto | rafael.roquetto at kdab.com<mailto:rafael.roquetto at kdab.com> | Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts - Platform-independent software solutions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121005/2b0dff9d/attachment.html>

More information about the Development mailing list