<?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>Sat, 22 Nov 2008 04:45:12 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Weier O'Phinney's Blog: Pastebin app updates]]></title>
      <guid>http://www.phpdeveloper.org/news/11108</guid>
      <link>http://www.phpdeveloper.org/news/11108</link>
      <description><![CDATA[<p>
<i>Matthew Weier O'Phinney</i> has <a href="http://weierophinney.net/matthew/archives/193-Pastebin-app-updates.html">made some updates</a> to his pastebin example showing the combination of the Zend Framework and Dojo libraries.
</p>
<blockquote>
I've been getting a lot of interest in my <a href="http://weierophinney.net/matthew/archives/189-Pastebin-app-and-conference-updates.html">Pastebin</a> demo app -- partly by those wanting to play with Dojo+ZF, partly by those just interested in the application. [...] I've created a <a href="http://github.com/weierophinney/pastebin/tree/master">Github repository</a> so you can track the latest developments, as well as pull custom tarballs.
</blockquote>
<p>
The demo application was a part of <i>Matthew</i>'s <A href="http://www.zend.com/en/webinar/Framework-Dojo/Webinar-Rec-Framework-Dev-EN-ZFDojo-20080903.flv">Zend Framework & Dojo</a> webinar from Zend.
</p>]]></description>
      <pubDate>Mon, 29 Sep 2008 10:23:25 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Expirmentalworks.net: Inofficial PHP GIT repositories - Importing large trees]]></title>
      <guid>http://www.phpdeveloper.org/news/9373</guid>
      <link>http://www.phpdeveloper.org/news/9373</link>
      <description><![CDATA[<p>
<i>David</i> has <a href="http://blog.experimentalworks.net/archives/61-Inofficial-PHP-GIT-repositories-Importing-large-trees.html">posted an article</a> to the Expirmentalworks.net blog about a task that he and <i>Johannes Schluter</i> have finished up - importing the PHP CVS tree over into <a href="http://git.or.cz/">Git</a>.
</p>
<blockquote>
A few month ago Johannes Schluter and I started discussing about GIT and other decentralized version control systems. During our exploration of GIT we thought about importing the PHP CVS tree into git. A few weeks later and a lot of wasted cpu time, we finally managed to provide an inofficial GIT mirror of the PHP CVS repository. It's provided by Johannes Schluter and mirrored by me. 
</blockquote>
<p>
<a href="http://blog.experimentalworks.net/archives/61-Inofficial-PHP-GIT-repositories-Importing-large-trees.html">The post</a> documents the path they followed - using git-cvsimport, parsecvs and a path they needed to make - to finally get the import working without any flaws. You can check out their unofficial repository <a href="http://www.schlueters.de/~johannes/git/?p=php/php-src.git;a=summary">here</a> (it's updates twice a day from the live CVS).
</p>]]></description>
      <pubDate>Tue, 08 Jan 2008 10:24:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Version Control Blog: Upgrading Drupal with Git]]></title>
      <guid>http://www.phpdeveloper.org/news/8408</guid>
      <link>http://www.phpdeveloper.org/news/8408</link>
      <description><![CDATA[<p>
On the Version Control Blog today there's <a href="http://versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/">a new guide</a> that helps to make upgrading your Drupal installation a simple and happy experience with the help of <a href="http://git.or.cz/">git</a> (the version control system).
</p>
<blockquote>
<p>
Drupal development team has released Drupal 5.2 on July 26, 2007. It fixes two security vulnerabilities, so it is highly recommended that you upgrade as soon as possible. Many Drupal installations often contain extra Drupal modules, and almost always the also contain local customizations. 
</p>
<p>
Question arises: how to upgrade your Drupal installations timely, safely, with confidence that none of your local customizations are lost; without need to remember each line that was edited and re-applying those edits to new version and without need to drastically change your workflow (very little discipline is needed actually).
</p>
</blockquote>
<p>
This <a href="http://versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/">detailed guide</a> walks you through the import of the source code, import of the Drupal modules and making the upgrades to the installation (drupal, drupal-and-modules and drupal-production) as well as how to resolve conflicts that might come up.
</p>]]></description>
      <pubDate>Wed, 08 Aug 2007 07:58:00 -0500</pubDate>
    </item>
  </channel>
</rss>
