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 27 and Version 28 of en/howto_release


Ignore:
Timestamp:
Dec 29, 2012, 11:31:34 AM (8 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/howto_release

    v27 v28  
    11= Releasing a new version of Jelix =
    22
    3 What should have been done to release a new version of jelix..
     3What should be done to release a new version of jelix..
    44
    55== maintenance release ==
     
    2828For major releases (new 1.x or x.0.0 version)
    2929
    30     - Update the manual content, update its version number etc..
    31     - check if this files are updated:
     30    - Update the manual content
     31    - Create a new branch on the manual repository, and set the new version number both on the new branch and on the master branch
     32    - reference the new manual branch in the configuration of docs.jelix.org
     33    - create the changelogs page in the web site: http://jelix.org/articles/en/changelog
     34        * the page dedicated to the branch should be updated with the list of improvements and bug fixed
     35        * don't forget similar pages in other languages, at least in french
     36    - check if this files are updated in the Jelix repository:
    3237        * README
    3338        * lib/jelix/CREDITS
    3439        * lib/jelix/INSTALL
    3540        * lib/jelix-modules/CREDITS
    36     - create the changelogs page in the web site: http://jelix.org/articles/en/changelog
    37         * the page dedicated to the branch should be updated with the list of improvements and bug fixed
    38         * don't forget similar pages in other languages, at least in french
    39     - for major stable release, create a new branch jelix-1.X.x
     41    - create a new branch jelix-1.X.x in the jelix repository
    4042    - execute the build/set_new_version.sh $NEWVERSION $NEXTVERSION on the new branch
    4143        * it will update VERSION files and add a tag like RELEASE_JELIX_X_Y_Z
    42     - Update this new files on the master branch, with the next major version number
     44    - Update these files on the master branch, with the next major version number
    4345        * lib/jelix/VERSION
    4446        * testapp/VERSION
    4547    - create packages locally with build/buildjelix.php and build/buildapp.php and test them
    4648    - update the controller of the homepage of the web site, add the branch number in the list
    47     - update all menu bar in all web sites to add link to the manual
     49    - update the template of home page to show the new stable branch
     50    - update all menu bar in some pages to add link to the manual (references page, wiki template)
    4851    - on the server, run
    4952        * {{{scripts/release $VERSION $NEXTVERSION}}} where $VERSION is the version number of the release (1.0.11 for example) and $NEXTVERSION, the future version to develop
    5053            * it will build package, manual, pdf, reference API, install them on download.jelix.org, close the roadmap in Trac, update wiki etc..
    5154        * update the script scripts/scripts.config.sh to set the new stable branch, for nightly builds
    52     - create a new download page on the web site http://jelix.org/articles/en/download/stable/1.x
     55        * update the BRANCHEVERSIONLIST variable in the nightlybuild script
     56    - create a new download page on the web site http://jelix.org/articles/en/download/stable/1.X
    5357    - update http://jelix.org/articles/en/download/stable and  http://jelix.org/articles/en/download/nightly
    54     - update the home page to set the new stable branch
    5558    - publish a news on jelix.org/news/,  in mailing lists and on tweeter
    5659