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 Initial Version and Version 1 of en/howto_release


Ignore:
Timestamp:
Nov 9, 2009, 11:47:40 AM (11 years ago)
Author:
laurentj
Comment:

ge

Legend:

Unmodified
Added
Removed
Modified
  • en/howto_release

    v1 v1  
     1= Releasing a new version of Jelix =
     2
     3What should have been done to release a new version of jelix..
     4
     5
     6== Maintenance release or new alpha/beta ==
     7
     8Instruction to release a new version for which we don't need to create a new branch:
     9
     10  * new version which fixes bugs for a specific stable branch
     11  * an alpha or beta version from the trunk
     12
     13
     14    - check if this files are updated:
     15        * README
     16        * lib/jelix/CREDITS
     17        * lib/jelix/INSTALL
     18        * lib/jelix-modules/CREDITS
     19    - update the version number in these files to reflect the new version
     20        * lib/jelix/VERSION
     21        * testapp/VERSION
     22    - update changelogs in the web site: http://jelix.org/articles/en/changelog
     23        * a page should be dedicated to the release, with the list of improvements and bug fixed
     24        * this page should be listed on the changelog page
     25        * don't forget similar pages in other languages
     26    - add a tag in the hg repository : RELEASE_JELIX_X_Y_Z  where X_Y_Z is the version number. ex: 1_1_3, 1_2_BETA1
     27    - create packages with build/buildjelix.php and build/buildapp.php
     28        * test them with testapp
     29        * check if all needed files are here
     30    - download packages on berlios.de
     31    - download packages on download.jelix.org
     32    - update home page of the web site
     33    - update the download page on the web site
     34    - update the API documentation on the web site (make docs)
     35    - create package for the API documentation on the web site, with phpdoc (make docs)
     36    - publish a news on jelix.org/news/
     37    - modify this files to reflect the next future version, with a "pre" prefix
     38        * lib/jelix/VERSION
     39        * testapp/VERSION
     40
     41== New major release ==
     42
     43Instruction to release a new major version of Jelix, from the trunk repository. A new branch should be created for futur minor versions. The main differences are last items in the list.
     44
     45    - check if this files are updated:
     46        * README
     47        * lib/jelix/CREDITS
     48        * lib/jelix/INSTALL
     49        * lib/jelix-modules/CREDITS
     50    - update the version number in these files to reflect the new version
     51        * lib/jelix/VERSION
     52        * testapp/VERSION
     53    - update changelogs in the web site: http://jelix.org/articles/en/changelog
     54        * a page should be dedicated to the release, with the list of improvements and bug fixed
     55        * this page should be listed on the changelog page
     56        * don't forget similar pages in other languages
     57    - add a tag in the hg repository : RELEASE_JELIX_X_Y_Z  where X_Y_Z is the version number. ex: 1_1_3, 1_2_BETA1
     58    - create packages with build/buildjelix.php and build/buildapp.php
     59        * test them with testapp
     60        * check if all needed files are here
     61    - download packages on berlios.de
     62    - download packages on download.jelix.org
     63    - update home page of the web site
     64    - update the download page on the web site
     65    - update the API documentation on the web site (make docs)
     66    - create package for the API documentation on the web site, with phpdoc (make docs)
     67    - publish a news on jelix.org/news/
     68
     69    - create a new branch, by creating a clone of the trunk repository to hg.jelix.org/releases/jelix-y.z.x
     70    - in the new branch,  modify this files to reflect the next minor future version, with a "pre" prefix
     71        * lib/jelix/VERSION
     72        * testapp/VERSION
     73    - in the trunk, modify this files to reflect the next major future version, with a "pre" prefix
     74        * lib/jelix/VERSION
     75        * testapp/VERSION
     76