I edited and updated the controls related change log here: https://codereview.qt-project.org/#change,84066
On a somewhat related note, I would suggest that for future updates we standardize on putting the bug-id after each item entry rather than in front as that would make the document a bit more readable in my opinion. I don’t really see any valid reason why people would remember a specific task number and scan that list manually. Jens On 24 Apr 2014, at 06:57, Thiago Macieira <thiago.macie...@intel.com<mailto:thiago.macie...@intel.com>> wrote: Em qua 23 abr 2014, às 21:22:40, Alan Alpert escreveu: On Tue, Apr 22, 2014 at 3:13 PM, Thiago Macieira <thiago.macie...@intel.com<mailto:thiago.macie...@intel.com>> wrote: Please find attached the raw logs for each of the modules that had any [ChangeLog] in the v5.2.1..origin/release range. I'm taking responsibility of editing the one for qtbase. For all other modules, I'd like someone to reply to this email saying they'll be the editor. Otherwise, there will be no changelog for the module at all, because I won't do it. I'll edit qtquick1. First draft at https://codereview.qt-project.org/#change,83982 (and it's just one item... probably ready to go). Also qtdeclarative, which I didn't see in the attachments, but running the script and adding the output to the existing changelog gives another 'first' draft: https://codereview.qt-project.org/#change,83983 Comments there. -- Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com> Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development