archive/php-src
1
0
Fork 0
mirror of https://github.com/php/php-src.git synced 2025-08-16 22:18:50 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Fix typos

Browse source
This commit is contained in:
Christoph M. Becker 2018-05-14 23:50:42 +02:00
parent 027dd86107
commit b9f99a3aed
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.RELEASE_PROCESS
View file

@ -37,7 +37,7 @@ Most developers should have this.
Moving extensions from php-src to PECL Moving extensions from php-src to PECL
- Checkout the pecl directory, most likely you want a sparse-root checkout - Checkout the pecl directory, most likely you want a sparse-root checkout
svn co --depth=empty https://svn.php.net/repository/pecl svn co --depth=empty https://svn.php.net/repository/pecl
- Create an directory for the extension incl. branch and tag structure, - Create a directory for the extension incl. branch and tag structure,
no trunk at this point and commit this to svn no trunk at this point and commit this to svn
cd pecl; mkdir foo foo/tags foo/branches; svn add foo; svn commit cd pecl; mkdir foo foo/tags foo/branches; svn add foo; svn commit
- Move the extension from php-src to the new location - Move the extension from php-src to the new location
@ -50,7 +50,7 @@ maintainers if any:
- create the package.xml, commit - create the package.xml, commit
- release the package - release the package
For Moving extensions from PECL to php-src the svn mv has to be tone the other For Moving extensions from PECL to php-src the svn mv has to be done the other
way round. way round.
Rolling a non stable release (alpha/beta/RC) Rolling a non stable release (alpha/beta/RC)
@ -188,7 +188,7 @@ credits files in ext/standard.
9. run: ``PHPROOT=. ./makedist php 5.4.1``, this will export the tag, create configure 9. run: ``PHPROOT=. ./makedist php 5.4.1``, this will export the tag, create configure
and build three tarballs (gz, bz2 and xz). and build three tarballs (gz, bz2 and xz).
Check if the pear files are updated (phar). Check if the pear files are updated (phar).
On some systems the behavior of GNU tar can default to produce POSIX complaint archives On some systems the behavior of GNU tar can default to produce POSIX compliant archives
with PAX headers. As not every application is compatible with that format, creation of with PAX headers. As not every application is compatible with that format, creation of
archives with PAX headers should be avoided. When packaging on such a system, the GNU tar archives with PAX headers should be avoided. When packaging on such a system, the GNU tar
can be influenced by defining the environment variable TAR_OPTIONS='--format=gnu'. can be influenced by defining the environment variable TAR_OPTIONS='--format=gnu'.
@ -365,7 +365,7 @@ New Release Manager Checklist
one or more of the previous RMs sign your key. Publish your public key to pgp.mit.edu with: one or more of the previous RMs sign your key. Publish your public key to pgp.mit.edu with:
`gpg --keyserver pgp.mit.edu --send-keys $KEYID` `gpg --keyserver pgp.mit.edu --send-keys $KEYID`
3. Request karma to eding main/php_version.h. Possibly karma for other restricted parts of 3. Request karma to edit main/php_version.h. Possibly karma for other restricted parts of
php-src might come in question. php-src might come in question.
4. Request karma for web/qa.git and web/php.git for publishing release announcements. 4. Request karma for web/qa.git and web/php.git for publishing release announcements.