You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Hasan (JIRA)" <ji...@apache.org> on 2011/02/23 02:15:38 UTC
[jira] Updated: (CLEREZZA-435) Coding convention compliance
[ https://issues.apache.org/jira/browse/CLEREZZA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hasan updated CLEREZZA-435:
---------------------------
Attachment: zz-coding-conventions.v1.txt
> Coding convention compliance
> ----------------------------
>
> Key: CLEREZZA-435
> URL: https://issues.apache.org/jira/browse/CLEREZZA-435
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Hasan
> Priority: Trivial
> Attachments: zz-coding-conventions.v1.txt
>
>
> This issue is about writing code which should comply to certain conventions within Clerezza's committer.
> An initial document on the coding conventions is attached to this issue.
> If you want to update Clerezza code so that it complies with these conventions, please use this issue number
> when you commit your changes. We might do this every now and then, therefore, please don't resolve and close this issue.
> Please DON'T use this issue number in your commit, if you also have other changes in the code besides changes
> due to coding conventions. If you could separate your commit in two steps, then it would be the best.
> One for the coding conventions (using this issue number in your commit) and the other for the fix due to the "real" issue
> you want to solve (using the respective issue number).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira