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 23 (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..

maintenance release

New version on a existing branch

  • 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
    • don't forget similar pages in other languages, at least in french
  • execute the build/set_new_version.sh $NEWVERSION $NEXTVERSION
    • it will update VERSION files and add a tag like RELEASE_JELIX_X_Y_Z
  • create packages locally with build/buildjelix.php and build/buildapp.php and test them
  • on the server, run
    • scripts/release $VERSION $NEXTVERSION where $VERSION is the version number of the release (1.0.11 for example) and $NEXTVERSION, the future version to develop
    • it will build package, manual, pdf, reference API, install them on download.jelix.org, close the roadmap in Trac, update wiki etc..
  • publish a news on jelix.org/news/

New branch

For major releases (new 1.x or x.0.0 version)

  • 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
  • create the changelogs page 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
    • don't forget similar pages in other languages, at least in french
  • for major stable release, create a new branch jelix-1.X.x
  • execute the build/set_new_version.sh $NEWVERSION $NEXTVERSION
    • it will update VERSION files and add a tag like RELEASE_JELIX_X_Y_Z
  • create packages locally with build/buildjelix.php and build/buildapp.php and test them
  • update the controller of the homepage of the web site, add the branch number in the list
  • update all menu bar in all web sites to add link to the manual
  • on the server, run
    • scripts/release $VERSION $NEXTVERSION where $VERSION is the version number of the release (1.0.11 for example) and $NEXTVERSION, the future version to develop
    • it will build package, manual, pdf, reference API, install them on download.jelix.org, close the roadmap in Trac, update wiki etc..
  • create a new download page on the web site http://jelix.org/articles/en/download/stable/1.x
  • update http://jelix.org/articles/en/download/stable and http://jelix.org/articles/en/download/nightly
  • publish a news on jelix.org/news/