Mailing-List: contact dev-help@clerezza.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@clerezza.apache.org
Date: Wed, 4 Dec 2013 15:04:36 +0000 (UTC)
From: =?utf-8?Q?Reto_Bachmann-Gm=C3=BCr_=28JIRA=29?= <jira@apache.org>
To: clerezza-dev@incubator.apache.org
Message-ID: <JIRA.12499429.1298423562044.70281.1386169476667@arcas>
In-Reply-To: <JIRA.12499429.1298423562044@arcas>
References: <JIRA.12499429.1298423562044@arcas>
Subject: [jira] [Assigned] (CLEREZZA-435) Coding convention compliance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLEREZZA-435?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reto Bachmann-Gm=C3=BCr reassigned CLEREZZA-435:
-------------------------------------------

    Assignee: Reto Bachmann-Gm=C3=BCr

> Coding convention compliance
> ----------------------------
>
>                 Key: CLEREZZA-435
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-435
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Hasan
>            Assignee: Reto Bachmann-Gm=C3=BCr
>            Priority: Trivial
>         Attachments: zz-coding-conventions.v1.txt
>
>
> This issue is about writing code which should comply to certain conventio=
ns 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 conven=
tions, please use this issue number
> when you commit your changes. We might do this every now and then, theref=
ore, 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.=20
> One for the coding conventions (using this issue number in your commit) a=
nd the other for the fix due to the "real" issue=20
> you want to solve (using the respective issue number).


--
This message was sent by Atlassian JIRA
(v6.1#6144)