pecl:releasing-a-pecl-package

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
pecl:releasing-a-pecl-package [2019/10/31 11:58] derickpecl:releasing-a-pecl-package [2019/10/31 12:35] (current) – Win builds may take some hours cmb
Line 26: Line 26:
     * ''pecl package-validate'' to check everything looks good     * ''pecl package-validate'' to check everything looks good
   * Run your tests (e.g. in CI)   * Run your tests (e.g. in CI)
-  * Recommended to create a tag in your VCS (e.g. ''git tag -s <version>'') and sign it with a GPG key if you can 
   * Use ''pecl package'' to generate a release ''.tgz'' file   * Use ''pecl package'' to generate a release ''.tgz'' file
   * Commit update to ''package.xml''   * Commit update to ''package.xml''
 +  * Recommended to create a tag in your VCS (e.g. ''git tag -s <version>'') and sign it with a GPG key if you can
   * Login and upload the ''.tgz'' to https://pecl.php.net/release-upload.php   * Login and upload the ''.tgz'' to https://pecl.php.net/release-upload.php
 +
 +For an example of a more comprehensive release process, it might be worth checking out https://github.com/xdebug/xdebug/blob/master/RELEASE_PROCESS.rst
 +
 +==== Windows binary packages ====
 +
 +Windows binary packages (including the DLLs) are supposed to be built and linked on the package page automatically. If that didn't happen several hours after the release, contact the PHP for Windows team via #winphp-dev on freenode IRC or email the pecl-dev list.
pecl/releasing-a-pecl-package.1572523132.txt.gz · Last modified: 2019/10/31 11:58 by derick