is not used any more and exists only for history. Post new tickets on the Github account. n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Changes between Version 2 and Version 3 of en/process

Mar 30, 2009, 11:17:17 AM (13 years ago)



  • en/process

    v2 v3  
    33The Jelix development process aims to drive to a quality developement.
     5== Peer-review ==
     7On the Jelix project, we follow a process of "peer-reviewing". Each modifications should be submit in a ticket, and an other developer will review your code before to include it into the repository of Jelix.
     9How does it happens:
     11 - a contributor propose a bug fix or an improvement by creating a patch. He attach this patch to a ticket in the bug tracker.
     12 - a reviewer reads the code of the patch, and verifies that the quality is good, the coding style is good, and the patch does things well.
     13 - all new features are also reviewed by one of the core developers.
     14 - when the patch is ok, the patch is commited in the repository, by the contributor if he has write access on the repository, or by an other developer.
     15 - each days, nightlies of jelix are built and are available in the download area ( And at the same time, all unit tests are executed and the result of this unit tests are mailed to the jelix-dev mailing list.
     18== Unit tests ==
     20Somte unit tests should be provided with each new features or bug fixed. It allow to verify that the framework is still working well, and to verify that there isn't any regressions.
    523== The actors ==
    927 * The contributors : they contribute by proposing patches, improvements. They don't have write access in the subversion repository.
    10  * The commiters : the regulqr contributors, those that "proved theselves" to be valuable. They have write access to the subversion repository. They are part of the project's team.
     28 * The commiters : the regular contributors, those that "proved theselves" to be valuable. They have write access to the subversion repository. They are part of the project's team.
    1129 * The reviewers : these are the commiters thar review the patches before giving agreement for commit. They necessarily deeply know the code of Jelix.
    1230 * The projet leader : He is warant of the respect to the roadmap, the consistency of the framework. He ensures that the changes are consistent with the objectives of the framework (lightness, performance, simplicity).
    15  * Les contributeurs : ils contribuent en proposant des patchs, des améliorations. Ils ne peuvent accéder en écriture au dépôt subversion.
    16  * Les "commiters" : les contributeurs réguliers, ceux qui ont fait "leur preuves". Ils ont accés en écriture au dépôt subversion. Ils font parti de l'équipe de développement du projet.
    17  * Les "reviewers" : ce sont des commiters qui relisent des patchs avant de donner l'accord d'un commit. Ils connaissent nécessairement le code de jelix en profondeur.
    18  * Le "projet leader" : celui qui a le dernier mot :-) Il est le garant du respect de la roadmap, de la cohérence du framework. Il s'assure que les évolutions sont compatibles avec les objectifs premiers du framework (légèreté, performance, simplicité).
    20 == The process ==
    22  - a contributor or a commiter propose a patch
    23  - a reviewer must review the code, check that the code respects the conventions, that it is optimized etc. Any modification must pass by a reviewer before being committed.
    24  - Any new features must also be approved by the project leader.
    25  - Once the patch is accepted, a comitter is in charge to integrate the patch in his local copy to check that the unit tests pass etc, and then commit.
    27 == Actual context ==
    29 Currently, because of the small number of contributors, there is only one reviewer, who is the actual project leader (Laurent).