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

Changes between Version 6 and Version 7 of en/process


Ignore:
Timestamp:
Aug 20, 2011, 9:55:24 AM (10 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/process

    v6 v7  
    55== Peer-review ==
    66
    7 On 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 official repository of Jelix.
     7On the Jelix project, we follow a process of "peer-reviewing". Each modifications should be submit in a ticket or committed in a "fork" in Github before a pull request, and an other developer will review your code before to include it into the official repository of Jelix.
    88
    99How does it happens:
    1010
    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. An other solution is to register on [http://bitbucket.org/ Bitbucket], "forking" [http://bitbucket.org/jelix/ an official repository of Jelix], making some change on your clone and requesting a pull. In this case, add a comment on the corresponding ticket to inform followers of the ticket about your changes.
     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. An other solution is to register on [http://github.com/ Github], "forking" [https://github.com/jelix/jelix the repository of Jelix], making some change on your clone and requesting a pull.
    1212 - 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.
    1313 - 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. In the case of a "pull" request on Bitbucket, the pull will be made.
    15  - each days, nightlies of jelix are built and are available in the download area (download.jelix.org). 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.
     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. In the case of a "pull" request on Github, the pull will be made.
     15 - each days, nightlies of jelix are built and are available in the download area (download.jelix.org). And at the same time, all unit tests are executed to verify that last commit didn't break something.
    1616
    1717
     
    2525Among the Jelix developpers, there are :
    2626
    27  * The contributors: they contribute by proposing patches, improvements. They don't have write access in the subversion repository.
    28  * The commiters: the regular contributors, those that "proved themselves" to be valuable. They have write access to the subversion repository. They are part of the project's team.
     27 * The contributors: they contribute by proposing patches, improvements. They don't have write access in the source code repository.
     28 * The commiters: the regular contributors, those that "proved themselves" to be valuable. They have write access to the repository. They are part of the project's team.
    2929 * The reviewers: these are the commiters thar review the patches before giving agreement for commit. They necessarily deeply know the code of Jelix.
    3030 * 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).