incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohammad Nour El-Din <>
Subject Re: commit messages and JIRA
Date Sun, 17 Jul 2011 18:56:28 GMT
A very big +1

I think we definitely SHOULD do that if not MUST. It helped me a lot
for tracing changes in my work. Also I would recommend something that
we use here, which I proposed and also helps to have double linking
between JIRA and SVN, that is when resolving the JIRA task I asked my
team to comment on that task with the revision number in which they
committed code related to that one.

On Sun, Jul 17, 2011 at 8:51 PM, Kevin Meyer - KMZ <> wrote:
> Hi Dan,
> Sounds like a plan - it'll also (help) ensure that JIRA tickets get created
> for all mods.
> Regards,
> Kevin
> On 17 Jul 2011 at 17:23, Dan Haywood wrote:
>> Now that we have a first release out, I'd like to ensure that there's
>> some traceability in changes being made...   That way we can be sure
>> that our release notes for subsequent releases will be reasonably
>> comprehensive, as well as meaning that users will gain confidence in us
>> as being a properly-run project.
>> So, what I'd like to propose that any commits that we do to the codebase
>> are cross-referenced to a JIRA ticket.  For example, if working on
>> ISIS-105, then the commit message should be something like: "ISIS-105:
>> sorted out formatting".
>> Opinions?
>> Thanks
>> Dan

- Mohammad Nour
  Author of (WebSphere Application Server Community Edition 2.0 User Guide)
- LinkedIn:
- Blog:
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship

"Stay hungry, stay foolish."
- Steve Jobs

View raw message