[Development] ChangeLogs

[Thiago Macieira]

On sexta-feira, 18 de janeiro de 2013 13.57.02, Sylvain Pointeau wrote:
> > And that leads to another downside: what if two or more commits were
> > necessary
> > to fix a bug? Then the ChangeLog line would be referring to changes that
> > are
> > not found in that commit, which could be confusing later on.
> 
>  And additionally what if you solve multiple bugs in one commit?
> 
> Normally you should indicate which bugs you are trying to solve with a
> commit
> And a reviewer should close the bug in the bug tracker.
> 
> Then the right way is to use the bug tracking tool to generate a change log.

If they are part of one single change, then it's likely we can word the 
changelog such that it explains both bug fixes.

If they are not part of the same change, then you should split in two commits 
anyway.
-- 
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/20130118/aa01bdbf/attachment.sig>