Hello everybody,
With all the problems on the 3.8, i think it is time to talk about "how
to develop".
It seems that too often, dolibarr code contributions are done with
little tests if any.
I dont want to point out one people or another so i dont give examples
here, but if a developer do some code improvement, he should :
* *know how the program works before touching it*
* *ask the dev or user mailing-list if he have any doubt about a feature
*
* *check after coding if the feaures that worked before are still working*
It seems to be the base of good coding, but it seems to be sometimes
forgotten or not known...
My two cents.
Christophe
---------------------------------------
/Christophe Battarel
Responsable technique Altairis/
+33 (0)9 52 71 70 96
Altairis <http://www.altairis.fr> - Blog <http://www.altairis.fr/blog> -
Modules Dolibarr <http://www.altairis.fr/modules>
_______________________________________________
Dolibarr-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
