Skip to content

Latest commit

 

History

History
38 lines (30 loc) · 1.54 KB

RELEASE_PROCESS.rst

File metadata and controls

38 lines (30 loc) · 1.54 KB
  1. Mantis: Create new version if needed, and move "Fixed in version" from -dev to release: https://bugs.xdebug.org/manage_proj_edit_page.php?project_id=1

  2. Make sure both the master and release branch (i.e. xdebug_3_0) are fully synced and merged.

  3. For first release in minor version (i.e. 3.1.x), merge package.xml from old bug fix branch into master and commit:

    git diff HEAD..xdebug_3_0 package.xml | patch -p1
    
  4. Run: php ~/bin/make-xdebug-release.php <version>

  5. Move existing release entry down in package.xml

  6. Include new snippet in /tmp/package.xml

  7. Run commands from output

  8. Update www.xdebug.org views/home/updates.php with snippet

  9. Update www.xdebug.org src/XdebugVersion.php with snippet

  10. Update pre-generated www.xdebug.org data/news/... file

  11. Write Patreon post taking the rendered news article as starting point

  12. Mantis: "release" the version, and make sure there is a new one.

  13. Wait until AppVeyor is ready

  14. In the release branch, update template.rc and php_xdebug.h to the new version

  15. Commit template.rc and php_xdebug.h with "Back to -dev"

  16. Check out master branch, and run: git merge --strategy=ours xdebug_3_0

  17. git push origin master xdebug_3_0

  18. Add files from AppVeyor and source to www.xdebug.org html/files

  19. Create sha256 files for the new releases:

    for i in *3.0.*{tgz,dll}; do

    echo $i; sha256sum $i | sed 's/.*//' > $i.sha256.txt;

    done

  20. Add the downloads, DDLs, SHA256 files, and news file to git and commit with "Go with 3.0.1"

  21. Upload the source package to PECL