Changelog quality

Alan Griffiths alan.griffiths at canonical.com
Fri Jun 6 14:52:00 UTC 2014


On 06/06/14 15:45, Cemil Azizoglu wrote:
> There is a discussion going on on ubuntu-phone about this. Having gone
> through the release process where I've had to make sure the changelog
> is accurate, I think it's a good time to discuss this within the team.
>
> Currently, we seem to complete the changelog when we release, which
> makes it difficult to come up with an accurate picture of what went
> into the release (unless you're Daniel, blessed with the
> attention-to-detail gene). I propose some ideas here, some of which
> are requested by the CI team:
>
> 1- Committer updates the changelog (as part of the same commit)

Yeah, get Tarmac to do it! ;)

If you really mean "proposer" then the problem is that all concurrent
MPs will be updating the file at the same point and that will quickly
lead to bzr merge conflicts.



More information about the Mir-devel mailing list