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 1 (modified by laurentj, 11 years ago) (diff)

ge

Releasing a new version of Jelix

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

Maintenance release or new alpha/beta

Instruction to release a new version for which we don't need to create a new branch:

  • new version which fixes bugs for a specific stable branch
  • an alpha or beta version from the trunk
  • check if this files are updated:
    • README
    • lib/jelix/CREDITS
    • lib/jelix/INSTALL
    • lib/jelix-modules/CREDITS
  • update the version number in these files to reflect the new version
    • lib/jelix/VERSION
    • testapp/VERSION
  • update changelogs in the web site: http://jelix.org/articles/en/changelog
    • a page should be dedicated to the release, with the list of improvements and bug fixed
    • this page should be listed on the changelog page
    • don't forget similar pages in other languages
  • 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
  • create packages with build/buildjelix.php and build/buildapp.php
    • test them with testapp
    • check if all needed files are here
  • download packages on berlios.de
  • download packages on download.jelix.org
  • update home page of the web site
  • update the download page on the web site
  • update the API documentation on the web site (make docs)
  • create package for the API documentation on the web site, with phpdoc (make docs)
  • publish a news on jelix.org/news/
  • modify this files to reflect the next future version, with a "pre" prefix
    • lib/jelix/VERSION
    • testapp/VERSION

New major release

Instruction to release a new major version of Jelix, from the trunk repository. A new branch should be created for futur minor versions. The main differences are last items in the list.

  • check if this files are updated:
    • README
    • lib/jelix/CREDITS
    • lib/jelix/INSTALL
    • lib/jelix-modules/CREDITS
  • update the version number in these files to reflect the new version
    • lib/jelix/VERSION
    • testapp/VERSION
  • update changelogs in the web site: http://jelix.org/articles/en/changelog
    • a page should be dedicated to the release, with the list of improvements and bug fixed
    • this page should be listed on the changelog page
    • don't forget similar pages in other languages
  • 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
  • create packages with build/buildjelix.php and build/buildapp.php
    • test them with testapp
    • check if all needed files are here
  • download packages on berlios.de
  • download packages on download.jelix.org
  • update home page of the web site
  • update the download page on the web site
  • update the API documentation on the web site (make docs)
  • create package for the API documentation on the web site, with phpdoc (make docs)
  • publish a news on jelix.org/news/
  • create a new branch, by creating a clone of the trunk repository to hg.jelix.org/releases/jelix-y.z.x
  • in the new branch, modify this files to reflect the next minor future version, with a "pre" prefix
    • lib/jelix/VERSION
    • testapp/VERSION
  • in the trunk, modify this files to reflect the next major future version, with a "pre" prefix
    • lib/jelix/VERSION
    • testapp/VERSION