- 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
- Make sure both the master and release branch (i.e. xdebug_3_3) are fully synced and merged.
For first release in minor version (i.e. 3.3.x), merge package.xml from old bug fix branch into master and new branch and commit:
git diff HEAD..xdebug_3_3 package.xml | patch -p1
- Run:
php .build.scripts/make-release.php <version>
- Move existing release entry down in
package.xml
- Include new snippet in
/tmp/package.xml
- Run commands from output
- Update www.xdebug.org
views/home/updates.php
with snippet - Update www.xdebug.org
src/XdebugVersion.php
with snippet - Update pre-generated www.xdebug.org
data/news/...
file - Write Patreon post taking the rendered news article as starting point
- Mantis: "release" the version, and make sure there is a new one.
- In the release branch, update template.rc and php_xdebug.h to the new version
- Commit template.rc and php_xdebug.h with
Back to -dev
- Check out master branch, and run:
git merge --strategy=ours xdebug_3_3
git push origin master xdebug_3_3
- Add files from GHA and source to www.xdebug.org html/files
Create sha256 files for the new releases:
for i in *3.2.*{tgz,dll}; do \ echo $i; sha256sum $i | sed 's/\ .*//' > $i.sha256.txt; \ done
- Add the downloads, DDLs, SHA256 files, and news file to git and commit with "Go with 3.3.2"
- Upload the source package to PECL