<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 18 Jun 2013 21:09:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Greg Beaver's Blog: If you run your own PEAR channel, please watch pear-qa]]></title>
      <guid>http://www.phpdeveloper.org/news/4933</guid>
      <link>http://www.phpdeveloper.org/news/4933</link>
      <description><![CDATA[<i>Greg Beaver</i> has <a href="http://greg.chiaraquartet.net/archives/118-if-you-run-your-own-PEAR-channel,-please-watch-pear-qa.html">a quick reminder</a> on his blog for anyone out there running their own PEAR channels - "please watch pear-qa".
<p>
<quote>
<i>
Just a quick note to all of you PEAR channel administrators: Please take a moment to either join the pear-qa@lists.php.net mailing list, or follow php.pear.qa at news.php.net.  Why?
<p>
Every time a new release of the core PEAR package is slated, I (or whoever is in charge of the release) will post a message to the pear-qa list asking for testing of the new version 1 full week ahead of the scheduled release date.  This is the one opportunity to test for critical errors that unit tests or myself have missed.
</i>
</quote>
<p>
There's a <a href="http://greg.chiaraquartet.net/archives/118-if-you-run-your-own-PEAR-channel,-please-watch-pear-qa.html">specific instance</a> he mentions of where this happened (in 1.4.7 involving channel names with a "-") and the code was still released. Of course, once it was applied, many users were upset that their installs had just "stopped working". 
<p>
<quote>
<i>
It would be very helpful to have channel administrators take a second to try out stable versions of PEAR as they approach release.
</i>
</quote>]]></description>
      <pubDate>Mon, 06 Mar 2006 07:11:40 -0600</pubDate>
    </item>
  </channel>
</rss>
