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 10 and Version 11 of en/howto_release


Ignore:
Timestamp:
Apr 7, 2011, 3:29:45 PM (10 years ago)
Author:
laurentj
Comment:

new publish_release.sh script on the server

Legend:

Unmodified
Added
Removed
Modified

  • en/howto_release

    v10 v11  
    2727        * create a new page for the next minor version
    2828    - 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
    29     - create packages with build/buildjelix.php and build/buildapp.php
    30         * test them with testapp
    31         * check if all needed files are here
    32     - download packages on berlios.de
    33     - download packages on download.jelix.org
    34     - update home page of the web site (through the svn repo of the web site)
    35     - update the download page on the web site
    36         * http://jelix.org/articles/en/download/stable
    37         * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of the next version
     29    - create packages localy with build/buildjelix.php and build/buildapp.php and test them
     30    - on the server, run
     31        * {{{install/publish_release.sh $BRANCH_VERSION $TAG_NAME $VERSION}}} where:
     32            * $BRANCH_VERSION is the name of the 'branch': 1.0.x, 1.1.x, 1.2.x
     33            * $TAG_NAME is the tag in the hg repository, for the release (RELEASE_JELIX_1_0_11 for example)
     34            * $VERSION  the version number of the release (1.0.11 for example)
     35        * it will create package and upload them on jelix.org and berlios.de
    3836    - build and update the API documentation on the web site, by running this command line on the server
    3937        * {{{install/build_release_doc $BRANCH_VERSION $TAG_NAME $VERSION}}} where:
    … …  
    4139            * $TAG_NAME is the tag in the hg repository, for the release (RELEASE_JELIX_1_0_11 for example)
    4240            * $VERSION  the version number of the release (1.0.11 for example)
    43     - update the html page on jelix.org/references/ to add links to the new api documentation (need access to the web site repository)
    4441    - optional: build and publish the manual, by running this command line on the server
    4542        * {{{install/build_release_manual $LANG $PAGE_ID $VERSION}}} where:
    … …  
    4744            * $PAGE_ID is the id of the first page of the manual. ex: en:manual-1.0
    4845            * $VERSION is the version of the release (1.0.11 for example)
     46    - update files pages on berlios.de
     47    - update home page of the web site (through the svn repo of the web site)
     48    - update the download page on the web site
     49        * http://jelix.org/articles/en/download/stable
     50        * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of the next version
     51    - update the html page on jelix.org/references/ to add links to the new api documentation (need access to the web site repository)
    4952    - publish a news on jelix.org/news/
    5053    - modify this files to reflect the next future version, with a "pre" suffix
    … …  
    7679        * create a new page for the next minor version for this new branch, and one for the next major version
    7780    - add a tag in the hg repository : RELEASE_JELIX_X_Y_0  where X_Y_0 is the version number. ex: 1_3_0
    78     - create packages with build/buildjelix.php and build/buildapp.php
    79         * test them with testapp
    80         * check if all needed files are here
    81     - download packages on berlios.de
    82     - download packages on download.jelix.org
    83     - update home page of the web site (through the svn repo of the web site)
    84     - update the download page on the web site
    85         * http://jelix.org/articles/en/download/stable and create a new page dedicated to the new branch
    86         * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of the next major and minor version
     81    - create packages with build/buildjelix.php and build/buildapp.php to test them
     82    - on the server, run
     83        * {{{install/publish_release.sh $BRANCH_VERSION $TAG_NAME $VERSION}}} where:
     84            * $BRANCH_VERSION is the name of the 'branch': 1.0.x, 1.1.x, 1.2.x
     85            * $TAG_NAME is the tag in the hg repository, for the release (RELEASE_JELIX_1_0_11 for example)
     86            * $VERSION  the version number of the release (1.0.11 for example)
     87        * it will create package and upload them on jelix.org and berlios.de
    8788    - build and update the API documentation on the web site, by running this command line on the server
    8889        * {{{install/build_release_doc $BRANCH_VERSION $TAG_NAME $VERSION}}} where:
    … …  
    9091            * $TAG_NAME is the tag in the hg repository, for the release (RELEASE_JELIX_1_0_11 for example)
    9192            * $VERSION  the version number of the release (1.0.11 for example)
    92     - update the html page on jelix.org/references/ to add links to the new api documentation (need access to the web site repository)
    9393    - optional: build and publish the manual, by running this command line on the server
    9494        * {{{install/build_release_manual $LANG $PAGE_ID $VERSION}}} where:
    … …  
    9696            * $PAGE_ID is the id of the first page of the manual. ex: en:manual-1.0
    9797            * $VERSION is the version of the release (1.0.11 for example)
     98    - update files pages on berlios.de
     99    - update home page of the web site (through the svn repo of the web site)
     100    - update the download page on the web site
     101        * http://jelix.org/articles/en/download/stable and create a new page dedicated to the new branch
     102        * http://jelix.org/articles/en/download/nightly by changing links to the nightlies of the next major and minor version
     103    - update the html page on jelix.org/references/ to add links to the new api documentation (need access to the web site repository)
    98104    - publish a news on jelix.org/news/
    99105    - create a new branch, by creating a clone of the trunk repository jelix-y.z.x