Prerequisites

Rolling a new release requires that the package to which the release belongs has been approved by the PEAR developers and that you have a valid PEAR website account. Information about meeting these two requirements can be found in the chapter Contributing your own code.

Please also read the various PEAR Group regulations that cover aspects like Version Naming, File Layout and other important topics not yet discussed in this manual. Furthermore there are a number of RFC's that followed these group regulations. These can be found under R for RFC in the finished PEPr proposals. Unfortunately these documents have not yet been included in a summarized coherent format in this manual. Please ask questions if you are in doubt about any of these documents.

Releasing A Package (Previous) Validating The Package Definition File (Next)
Last updated: Thu, 31 Jul 2014 — Download Documentation
Do you think that something on this page is wrong? Please file a bug report or add a note.
View this page in:

User Notes:

Note by: doconnor
A good tool to help you generate a valid package.xml for your code is PEAR_PackageFileManager_Cli.

You can see the documentation @ http://pyrus.sourceforge.net/PEAR_PackageFileManager_Cli.html

This will help you quickly create, edit and write out package.xml files.