It is not a best practice, it is mandatory practice, as we have indicated in several other mails about having proper commit log messages.
Thanks Azeez On Sun, Jan 16, 2011 at 1:49 PM, Sameera Jayasoma <[email protected]> wrote: > Hi Folks, > > Lets make it a best practise to put the Jira key (e.g. CARBON-8161) with > the commit message. Take a look at the issue [1]. Select the "Subversion > commits" tab. > > This will give us easy access to the commit messages, revision numbers, > modified files related to a given issue. > > Sample commit message would be; > > *Fixing JIRA Issue CARBON-8161 <https://wso2.org/jira/browse/CARBON-8161>* > > Thanks > Sameera > > [1] https://wso2.org/jira/browse/CARBON-8161 > > -- > Sameera Jayasoma > Technical Lead and Product Manager, WSO2 Carbon > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
