Le 23/12/2015 19:28, Taher Alkhateeb a écrit :
Ok so perhaps a middle ground is to have a central JIRA issue to which I
refer all commits. This way I can be lean in cleaning up the code base.
Clearly it's good point to have a central issue, and maybe commit group
by cover.
Nicolas
to cleanup the code base but not sure whether a
JIRA issue is necessary.
Do i need to issue a JIRA for pure code refactoring (no functional change)?
This would include things like function and variable rename, breaking up
big classes and functions, adding unit tests, rewiring classes and so
; Jacques
>
>
> Le 23/12/2015 18:33, Taher Alkhateeb a écrit :
>
>> Hi everyone,
>>
>> Many times I have the itch to cleanup the code base but not sure whether a
>> JIRA issue is necessary.
>>
>> Do i need to issue a JIRA for pure code refactori
Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Wed, Dec 23, 2015 at 6:33 PM, Taher Alkhateeb <slidingfilame...@gmail.com
> wrote:
> Hi everyone,
>
> Many times I have the itch to cleanup the code base but not sure whether a
> JIRA issue is necessary.
>
> Do i need to issu
Hi Everyone,
Many times I feel the necessity to refactor and cleanup the code base and I
don't see a necessity for issuing a JIRA for that.
Do we have a policy on pure refactoring (no functional change)? I would
like to refactor code without issuing a JIRA. Examples are function and
variable
Hi everyone,
Many times I have the itch to cleanup the code base but not sure whether a
JIRA issue is necessary.
Do i need to issue a JIRA for pure code refactoring (no functional change)?
This would include things like function and variable rename, breaking up
big classes and functions, adding
issue, for people
to refer in a sole place in case of need.
Jacques
Le 23/12/2015 18:33, Taher Alkhateeb a écrit :
Hi everyone,
Many times I have the itch to cleanup the code base but not sure whether a
JIRA issue is necessary.
Do i need to issue a JIRA for pure code refactoring (no functional
