[Development] How to release critical fixes?

Thiago Macieira thiago.macieira at intel.com
Fri Oct 5 18:53:42 CEST 2012

On sexta-feira, 5 de outubro de 2012 15.13.22, shane.kearns at accenture.com 
> Since the major/minor/patch release is encoded into QT_VERSION, critical
> releases should increment the patch number. I suggest to use a short lived
> branch for just this release.
> e.g.
> check out previous patch release tag (e.g. v4.8.3)
> create a branch from it
> cherry pick the critical fix(es) onto the branch
> cherry pick the QT_VERSION update to the branch
> tag the head of the branch with the new release (e.g. v4.8.4)
> close the branch
> push a QT_VERSION update to the main branch (e.g. 4.8) to update the
> QT_VERSION to the next release (e.g. 4.8.5)

I agree with this workflow. It matches what I said last week about the Qt 5 
security releases for past versions, but I hadn't included the security 
releases for the *current* version.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121005/63dfd72c/attachment.sig>

More information about the Development mailing list