cvs: phd(PHD_0_4) / HOWTO.RELEASE

From: Date: Mon, 16 Feb 2009 18:39:16 +0000
Subject: cvs: phd(PHD_0_4) / HOWTO.RELEASE
Groups: php.doc.cvs 
Request: Send a blank email to doc-cvs+get-3285@lists.php.net to get a copy of this message
cweiske Mon Feb 16 18:39:16 2009 UTC Added files: (Branch: PHD_0_4) /phd HOWTO.RELEASE Log: add release howto http://cvs.php.net/viewvc.cgi/phd/HOWTO.RELEASE?view=markup&rev=1.1 Index: phd/HOWTO.RELEASE +++ phd/HOWTO.RELEASE How to release a new version of PhD ----------------------------------- Releases are currently made from the PHD_0_4 branch. Changes in HEAD are merged back into that branch. 0. Check if all changes in HEAD have been merged back to the release branch. 1. Check if all changes have an entry in package.xml's <notes>. 2. Check if the api version needs to be increased to match the release version. (This is the case when the API has changed. Normally the committer has done that already when merging from HEAD, but you'll never know). 3. Make sure all files are listed in package.xml's <content>. 4. Edit config.php and set PHD_VERSION to the current one. 5. $ pear package $ pear install PhD-*.tgz .. try phd on phpdoc and peardoc .. $ pear cvstag package.xml 6. Upload the tgz to http://doc.php.net/up.php 7. Test by installing from the channel: $ pear upgrade -f doc.php.net/phd-$previousversion $ pear upgrade doc.php.net/phd-$thisstability .. try phd on phpdoc and peardoc .. 8. Let Hannes update http://doc.php.net/phd/ 9. Send release mail to phpdoc@ and pear-doc@lists.php.net A. Remove all contents from <notes> and increase version/release. Change stability back to "snapshot". Revert PHD_VERSION in config.php back to "phd-from-cvs". B. Hack on.

« previous php.doc.cvs (#3285) next »