|Re: [cross-project-issues-dev] Must all changes be tracked by a bug?|
On 09/02/2016 09:20 AM, Wim Jongman wrote:
I'm taking the risk of being convicted here, but for SWTBot, we don't enforce a Bugzilla.
So, for SWT, here is how we allow things to happen
If a bugzilla is already existing for the project, we ask the contributor to link to bug in commit message, usually on first line. If this is someone "new" to us, we try to explain how to amend and push again the commit, or to use Gerrit online edition for that (pretty useful), or we edit the message and comment explaining that we added a reference to the bug (so contributor understands what we edit and why, as it's not obvious).
If there is a bug existing, we usually ask to provide the Bugzilla in commit message.
If there is a Gerrit which is not linked to a bugzilla automatically, then we add the Gerrit URL to the "See also" of the bug.
Because AFAIK, people are not forced to create a bug for each code change. At least, committers don't have too IIRC.
The changelog from Git is a decent documentation if commit messages are well written. With the rise of code-review, there are less "noisy" commits, so reading the changelog just seems like a better documentation than sorting out the right Bugzilla request.
Back to the top