[Releasing] [Development] How to release critical fixes?
Sergio.Ahumada at digia.com
Fri Oct 5 16:49:51 CEST 2012
I think this is the right place to discuss this.
but, how many other releases are we planning for 4.8.x ? I think it's better to focus on the Qt 5 release process that Thiago sent some days ago.
Quality Engineer - Digia, Qt
From: development-bounces+sergio.ahumada=digia.com at qt-project.org [development-bounces+sergio.ahumada=digia.com at qt-project.org] on behalf of Rafael Roquetto [rafael.roquetto at kdab.com]
Sent: Friday, October 05, 2012 16:32
To: development at qt-project.org
Subject: [Development] How to release critical fixes?
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 | 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
More information about the Releasing