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 18 and Version 19 of en/howto_release


Ignore:
Timestamp:
Dec 28, 2012, 6:40:12 PM (9 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/howto_release

    v18 v19  
    33What should have been done to release a new version of jelix..
    44
    5     - Update the manual content, update its version number etc..   
     5== maintenance release ==
     6
     7New version on a existing branch
     8
     9    - Update the manual content, update its version number etc..
    610    - check if this files are updated:
    711        * README
     
    1115    - update changelogs in the web site: http://jelix.org/articles/en/changelog
    1216        * the page dedicated to the branch should be updated with the list of improvements and bug fixed
    13         * create this page for new branch
    14         * don't forget similar pages in other languages
    15     - for major stable release, create a new branch jelix-1.X.x
     17        * don't forget similar pages in other languages, at least in french
    1618    - update the version number in these files to reflect the new version
    1719        * lib/jelix/VERSION
     
    2022    - add a tag on the branch: RELEASE_JELIX_X_Y_Z  where X_Y_Z is the version number. ex: 1_1_3, 1_2_BETA1
    2123    - create packages locally with build/buildjelix.php and build/buildapp.php and test them
    22     - If this is a new branch
    23         * update the controller of the homepage of the web site, add the branch number in the list
    24         * update all menu bar in all web sites to add link to the manual
    2524    - on the server, run
    2625        * {{{scripts/release $VERSION}}} where $VERSION is the version number of the release (1.0.11 for example)
    2726        * it will build package, manual, pdf, reference API and install them on download.jelix.org
    2827    - update the download page on the web site
    29         * http://jelix.org/articles/en/download/stable  and for a major release, create a new page dedicated to the new branch
    30         * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of next versions
     28        * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of next versions for testapp
    3129    - publish a news on jelix.org/news/
    3230    - modify this files to reflect the next future version, with a "pre" suffix, on the release branch, and for a major release, on the master branch
     
    3836        * create a roadmap for the next version (minor and major if necessary)
    3937        * add the released version in the list of versions
     38
     39== New branch ==
     40
     41For major releases (new 1.x or x.0.0 version)
     42
     43    - Update the manual content, update its version number etc..
     44    - check if this files are updated:
     45        * README
     46        * lib/jelix/CREDITS
     47        * lib/jelix/INSTALL
     48        * lib/jelix-modules/CREDITS
     49    - create the changelogs page in the web site: http://jelix.org/articles/en/changelog
     50        * the page dedicated to the branch should be updated with the list of improvements and bug fixed
     51        * don't forget similar pages in other languages, at least in french
     52    - for major stable release, create a new branch jelix-1.X.x
     53    - update the version number in these files to reflect the new version, in the new branch
     54        * lib/jelix/VERSION
     55        * lib/jelix/CHANGELOG
     56        * testapp/VERSION
     57    - add a tag on the branch: RELEASE_JELIX_X_Y_Z  where X_Y_Z is the version number. ex: 1_1_3, 1_2_BETA1
     58    - create packages locally with build/buildjelix.php and build/buildapp.php and test them
     59    - update the controller of the homepage of the web site, add the branch number in the list
     60    - update all menu bar in all web sites to add link to the manual
     61    - on the server, run
     62        * {{{scripts/release $VERSION}}} where $VERSION is the version number of the release (1.0.11 for example)
     63        * it will build package, manual, pdf, reference API and install them on download.jelix.org
     64    - create a new download page on the web site http://jelix.org/articles/en/download/stable/1.x
     65    - update http://jelix.org/articles/en/download/stable
     66    - update http://jelix.org/articles/en/download/nightly by adding links to the nightlies of next versions
     67    - publish a news on jelix.org/news/
     68    - modify this files to reflect the next future version, with a "pre" suffix, on the release branch and on the master branch
     69        * lib/jelix/VERSION
     70        * lib/jelix/CHANGELOG
     71        * testapp/VERSION
     72    - on the bug tracker
     73        * close the corresponding roadmap
     74        * create a roadmap for the next version (minor and major if necessary)
     75        * add the released version in the list of versions
     76