Jacques, inline.
Am 12.09.16 um 15:51 schrieb Jacques Le Roux:
Please do not start to question the blog style/format now, we use it for months, you reviewed it for month and did not raise such a question anytime in the past. Why now?the parenthesis comes from our blog post format where we put the JIRA issue reference just behind the title (you know it because we are working together on this every month).Sorry, I did not notice this aspect. Do we really need parenthesis there, what does it add. A simple list separated by spaces would not be enough? It seems it would even easier to read to me.
And I clearly stated that the below commit is an exception, we normally only have one issue reference per commit. And following Gil's smart suggestion, the other Jira references could go in the details section without the parenthesis. I would be fine with that.Of course, we can parse without the parenthesis and set them when we generate the development details. But again, we already agreed upon this format and I don't see a big effort for a committer to put parenthesis around the Jira issue.Sorry, I see a big difference with commits like the one below!
The above example is an exception when it comes to effort. We normally have one JIRA reference in the commit messages.When I count the time we already spent discussing these nitpicking details, you could have written a whole bunch of correct commit messages in this time. You are making it very hard to establish such a simple guideline.Again, I really don't see the need for the parenthesis. And I'd be happy to change that myself once in wiki and elsewhere it's needed rather than have to type it every time I commit (yes I commit a lot :p)
Please, Jacques, that's ridiculous.You already have checked in your personal Tortoise template in SVN, you didn't have to type anything except the Jira number for this part of the commit message.
Until now, you seem to be the only one objecting against the proposed format, other committers have given +1 and showed support for it. They even use it right now.
But I will not stick to the proposal if there are other objections. So fellow committers, let's hear what you think. Thanks, Michael
smime.p7s
Description: S/MIME Cryptographic Signature
