wiki:en/howto_release
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.

Version 17 (modified by laurentj, 8 years ago) (diff)

--

Releasing a new version of Jelix

What should have been done to release a new version of jelix..

  • Update the manual content, update its version number etc..
  • check if this files are updated:
    • README
    • lib/jelix/CREDITS
    • lib/jelix/INSTALL
    • lib/jelix-modules/CREDITS
  • update changelogs in the web site: http://jelix.org/articles/en/changelog
    • the page dedicated to the branch should be updated with the list of improvements and bug fixed
    • create this page for new branch
    • don't forget similar pages in other languages
  • for major stable release, create a new branch jelix-1.X.x
  • update the version number in these files to reflect the new version
    • lib/jelix/VERSION
    • lib/jelix/CHANGELOG
    • testapp/VERSION
  • 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
  • create packages locally with build/buildjelix.php and build/buildapp.php and test them
  • on the server, run
    • install/build_release_pack $BRANCH_VERSION $TAG_NAME $VERSION where:
      • $BRANCH_VERSION is the name of the 'branch': 1.0.x, 1.1.x, 1.2.x
      • $TAG_NAME is the tag in the repository, for the release (RELEASE_JELIX_1_0_11 for example)
      • $VERSION the version number of the release (1.0.11 for example)
    • it will create package and install them on download.jelix.org
  • build and update the API documentation on the web site, by running this command line on the server
    • install/build_release_doc $BRANCH_VERSION $TAG_NAME $VERSION where:
      • $BRANCH_VERSION is the name of the 'branch': 1.0.x, 1.1.x, 1.2.x or trunk
      • $TAG_NAME is the tag in the repository, for the release (RELEASE_JELIX_1_0_11 for example)
      • $VERSION the version number of the release (1.0.11 for example)
  • in directory of the docs.jelix.org website run ./update_repo_and_books.sh --force to build latest version of the manual
  • in download.jelix.org/jelix/documentation/en/ (and fr/), copy the file jelix-manual-1.x.pdf to jelix-manual-1.x.y.pdf
  • update the home page of the web site
  • update the download page on the web site
  • update the html page on jelix.org/references/ to add links to the new api documentation
  • publish a news on jelix.org/news/
  • 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
    • lib/jelix/VERSION
    • lib/jelix/CHANGELOG
    • testapp/VERSION
  • on the bug tracker
    • close the corresponding roadmap
    • create a roadmap for the next version (minor and major if necessary)
    • add the released version in the list of versions