[Development] Cleaner code base patches

Thiago Macieira thiago.macieira at intel.com
Mon Jan 28 19:04:40 CET 2013


On segunda-feira, 28 de janeiro de 2013 17.03.39, Rutledge Shawn wrote:
> On 28 Jan 2013, at 5:39 PM, Sune Vuorela wrote:
> > On 2013-01-28, Knoll Lars <Lars.Knoll at digia.com> wrote:
> >>>> 1) always with -developer-build
> >>>> 2) on by default on -developer-build, but the CI disables it
> >>>> 3) completely optional, CI enables it
> >>>> 4) completely optional, not enabled by the CI
> >> 
> >> I'd favor (2) for now, and move over to (1) once we gained a little
> >> experience with it for the compilation of the whole module. The header
> >> compilation test should probably move to (1) immediately.> 
> > Can something in the 'middle' be done where CI somehow yells at
> > people who introduces new warnings?
> 
> That could maybe be another bot like the doc and sanity bots.  Or maybe the
> sanity bot could do it.

I'd rather skip that step and simply go to -Werror. Lars proposed that we 
experiment with it a little and see how far it goes before turning it on.

The good thing about -Werror is that the failure comes fast.
-- 
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/20130128/2b7277cb/attachment.sig>


More information about the Development mailing list