On 02/19/2013 07:34 AM, Christoph Kutzinski wrote:
what if you forgot to put ‘[FIXED JENKINS-12345]’ into the commit message. If
it haven't been released, yet, it's certainly easy to add a 'bogus' commit with
that
message, but what if it was already released?
There might need to be a way to add exceptions for cases like these, but I would hope it is easier to drill into people’s heads that commit messages must mention a filed
issue than that an entry must be added to a specific section of a separate changelog.html.
what if you want to add more info in the changelog
Just put it in the commit message; or say to see JIRA for more background and
details. Most changelog entries today are just one short line anyway.
To put things into perspective, compare the current 1.480.3 changelog [1] with the actual contents of the release according to git log [2]. The latter is admittedly
tidied up by hand, but what is more important is how much is outright missing from the former.
[1] http://jenkins-ci.org/changelog-stable
[2] http://release-notes.cloudbees.com/release/Jenkins+OSS+LTS/1.480.3
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
