[ 
https://issues.apache.org/jira/browse/SOLR-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201529#comment-14201529
 ] 

Shawn Heisey commented on SOLR-6654:
------------------------------------

bq. If i am fixing an issue , that means the first commit, what should be the 
message? isn't it same as the issue description?. OTOH , if I am doing an extra 
commit to make some enhancements to the same issue , I can explicitly specify 
the enhancement

I would say that the minimum message should include the issue summary (title).  
When the issue number is the only thing in the message, most people will not 
remember what that issue is for, so if they want to know, they have to go look 
it up.  That might be hard to do in some circumstances ... for instance, you 
might be skimming email on a phone or other mobile device, or you might be 
reviewing "svn log" output.  If there's a meaningful message, I can decide 
immediately on reading the commit email whether I need/want to look at the 
issue for more detail.

Commit messages are by developers, for developers ... so it's helpful to have a 
message that describes the *commit* and includes a little more detail.  Other 
summaries (like CHANGES.txt) are for users ... developer detail there tends to 
just cause confusion.

I don't know if you know this ... but there is a comm...@lucene.apache.org 
mailing list.  Each commit will result in at least one email (revision 1633340 
was 19 messages, and I've seen larger ones), showing the revision number, 
commit message, and the full diff.  Unlike the Commit Bot messages that get 
added to the Jira issue, you cannot see any other details, like the issue 
summary.  I rely on the commits list more than the Jira updates for staying 
aware of code updates.  I use the messages in my Jira folder to stay informed 
of Jira discussions, and mostly skip over the Commit Bot messages, because they 
do not include the diff.


> add a standard way to listen to config changes in cloud mode
> ------------------------------------------------------------
>
>                 Key: SOLR-6654
>                 URL: https://issues.apache.org/jira/browse/SOLR-6654
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to