On segunda-feira, 25 de novembro de 2013 13:08:28, Alan Alpert wrote: > I'm happy to have it warn though. That's +0, and a comment along the > lines of "ChangeLog: Commit message references a task but does not > include a ChangeLog message. If the task is >=P2 and affected previous > versions, please add a ChangeLog entry"(I'm not hung up on the > wording, that's just what I'd write).
After doing the ChangeLog for QtCore, here's what I think are worthy of changelog entries: - Any behaviour change of front-end API - important bugfixes - deprecations - new classes, enums and members (for a new class, an "Added XXX class that can be used to do foo" is enough) The changelog is more detailed for changes to existing functionality, as people can read the documentation for new things and decide whether they want to use it. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
