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


Ignore:
Timestamp:
Dec 7, 2012, 6:03:28 PM (8 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/howto_release

    v17 v18  
    2020    - 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
    2121    - 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
    2225    - on the server, run
    23         * {{{install/build_release_pack $BRANCH_VERSION $TAG_NAME $VERSION}}} where:
    24             * $BRANCH_VERSION is the name of the 'branch': 1.0.x, 1.1.x, 1.2.x
    25             * $TAG_NAME is the tag in the repository, for the release (RELEASE_JELIX_1_0_11 for example)
    26             * $VERSION  the version number of the release (1.0.11 for example)
    27         * it will create package and install them on download.jelix.org
    28     - build and update the API documentation on the web site, by running this command line on the server
    29         * {{{install/build_release_doc $BRANCH_VERSION $TAG_NAME $VERSION}}} where:
    30             * $BRANCH_VERSION is the name of the 'branch': 1.0.x, 1.1.x, 1.2.x or trunk
    31             * $TAG_NAME is the tag in the repository, for the release (RELEASE_JELIX_1_0_11 for example)
    32             * $VERSION  the version number of the release (1.0.11 for example)
    33     - in directory of the docs.jelix.org website run {{{./update_repo_and_books.sh --force}}} to build latest version of the manual
    34     - in download.jelix.org/jelix/documentation/en/ (and fr/), copy the file jelix-manual-1.x.pdf to jelix-manual-1.x.y.pdf
    35     - update the home page of the web site
     26        * {{{scripts/release $VERSION}}} where $VERSION is the version number of the release (1.0.11 for example)
     27        * it will build package, manual, pdf, reference API and install them on download.jelix.org
    3628    - update the download page on the web site
    3729        * http://jelix.org/articles/en/download/stable  and for a major release, create a new page dedicated to the new branch
    3830        * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of next versions
    39     - update the html page on jelix.org/references/ to add links to the new api documentation
    4031    - publish a news on jelix.org/news/
    4132    - 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