[Development] RFC: What constitutes a "non-destabilising" bug-fix?

Thiago Macieira thiago.macieira at intel.com
Fri Jan 11 16:40:39 CET 2013


On sexta-feira, 11 de janeiro de 2013 15.21.43, Olivier Goffart wrote:
> Go to stable:
>   a. Fixes to regressions against a previous "recent" version of Qt. (less
>       than 2 or 3 years old)
>   b. Fixes in new feature introduced in the most recent minor version.
>   c. Critical fixes (P1/P0): security, crashes or data corruption.
>   d. Compilation fixes or adaptations required for different version of the
>       compilers or upstream libraries.
> Everything else go to dev.

I agree with almost all: I'd like to relax "c" to include Important (P2) fixes, 
subject to the approvers' decision. Those should happen most commonly in the 
first one or two patch releases (.0 and .1).

-- 
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/20130111/2eca6ac1/attachment.sig>


More information about the Development mailing list