Using new features at pear.php.net

Hi everyone, A few important new features at pear.php.net will remove confusion over two important issues: version number selection and package.xml contents. If you browse to the homepage for a package, these features are apparent when logged in. Let's say you maintain a package like PHP_Parser. Browse to http://pear.php.net/PHP_Parser On the right, you will see: * Next Bugfix release should be: 0.1.1, stability devel * Next New Feature release should be: 0.2.0, stability alpha The 0.1.1and 0.2.0 links are clickable, and will bring you to a roadmap creation page. Once you have created the roadmap, 2 links will be visible that say: Add Bugs/Features to this Roadmap Generate package.xml for this release Click "Add Bugs/Features to this Roadmap" and choose from bugs closed since the last release, clicking their checkboxes. Afterwards, click the "Return to Roadmap Manager" link, and click "Generate package.xml for this release" Voila - based on the previous release's package.xml file contents, you have a brand new package.xml that can be cut/pasted. The only thing that may need to be updated is the <contents> tag if you have added files, even the changelog is managed for you. Now, let's say you have a new package and have not done any releases, like the PEAR_ErrorStack package. Browse to http://pear.php.net/PEAR_ErrorStack, and you'll see: First release should be version 0.1.0, stability alpha Click on the "0.1.0" and create the roadmap. Now, since this is the first release, there are no bugs/features to add, so directly click "Generate package.xml for this release" and voila, you have a brand new package.xml template. Note that this section: <contents> <dir name="/"> <file name="ADDFILESHERE" role="php" /> </dir> <!-- / --> </contents> will have to be modified for the package to work, but now there is no guesswork needed, no scripts, nothing beyond a publicly documented roadmap. PEAR just got a whole lot easier to develop for. Greg