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 31 and Version 32 of en/howto_release


Ignore:
Timestamp:
Apr 15, 2021, 12:02:46 AM (4 months ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/howto_release

    v31 v32  
    2121    - create a new tag on jelix-standard repos
    2222    - create packages locally with build/buildjelix.php and build/buildapp.php and test them
    23     - on the server, run
    24         * {{{scripts/release $VERSION}}} where $VERSION is the version number of the release (1.0.11 for example)
    25         * it will build package, manual, pdf, reference API, install them on download.jelix.org, update wiki etc..
    26     - create a release on github with built packages
     23    - push new commits and tag on the gitlab instance : it will generate packages and API doc, and it will publish packages on download.jelix.org
     24    - push new commits and tag on github and create a release on github with built packages
    2725    - update version in api/ on jelix.org
    2826    - publish a news on jelix.org/news/,  in mailing lists and on tweeter
     
    4442        * lib/jelix-modules/CREDITS
    4543    - create a new branch jelix-1.X.x in the jelix repository
    46     - execute the build/set_new_version.sh $NEWVERSION $NEXTVERSION on the new branch
     44    - update scripts of the build machine for the CI, to take care of the new branch
     45    - execute the php build/set_new_version.php $NEWVERSION $NEXTVERSION on the new branch
    4746        * it will update VERSION files and add a tag like RELEASE_JELIX_X_Y_Z
    48         * ex: NEWVERSION=1.6.4 NEXTVERSION=1.6.5pre.SERIAL
    49     - Update these files on the master branch, with the next major version number
    50         * lib/jelix/VERSION
    51         * testapp/VERSION
     47        * ex: NEWVERSION=1.7.2 NEXTVERSION=1.7.3-pre
     48    - execute the php build/set_new_version.php $NEXTMAJORVERSION on the master branch, where $NEXTMAJORVERSION is the new major version of master, with a suffix -pre
    5249    - create packages locally with build/buildjelix.php and build/buildapp.php and test them
    53     - create a release on github with built packages
     50    - push new commits and tag on the gitlab instance : it will generate packages and API doc, and it will publish packages on download.jelix.org
     51    - push new commits and tag on github and create a release on github with built packages
    5452    - create a new tag on jelix-standard repos
    5553    - update the controller of the homepage of the web site, add the branch number in the list
    5654    - update the template of home page to show the new stable branch
    5755    - update all menu bar in some pages to add link to the manual (references page, wiki template)
    58     - on the server, run
    59         * {{{scripts/release $VERSION}}} where $VERSION is the version number of the release (1.0.11 for example)
    60             * it will build package, manual, pdf, reference API, install them on download.jelix.org, update wiki etc..
    61         * update the script scripts/scripts.config.sh to set the new stable branch, for nightly builds
    62         * update the BRANCHEVERSIONLIST variable in the nightlybuild script
    6356    - create a new download page on the web site http://jelix.org/articles/en/download/stable/1.X
    6457    - update http://jelix.org/articles/en/download/stable and  http://jelix.org/articles/en/download/nightly