Packaging The Release Tarball

Now that your package has a valid package definition file, you can package
the release tarball. Cd to the top-level directory of the package and run:
pear package
This will create the release tarball that will be used later to upload the
new release.

Please note that the zlib extension needs to be enabled in
your PHP build in order to create the release tarball.

Next, you should install the package locally by running: pear
install <file> (file is the
tarball you just created). This is done to ensure that the package
definition file is not only valid but also contains valid
information. You should manually check that every file is installed
in the right place. If your package contains test scripts, which is
highly recommended, you should run them.

If anything fails at this stage, correct it and re-package and re-test.
When everything seems OK, proceed.

User Notes:

At this point, it's often a good idea to commit your altered package.xml back to SVN.

You can 'tag' a release in the repository. You can do this via the normal SVN tag mechanism in most cases, but for some packages (ie; Validate) this isn't appropriate - there are many fragments of different packages, and not all of them are in your release.

The pear command line tools include a simple `pear svn-tag`, which will inspect your package.xml and create a tag for you.