<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Drupal 4.7 RC3</title>
	<atom:link href="http://www.darcynorman.net/2006/04/15/drupal-4-7-rc3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darcynorman.net/2006/04/15/drupal-4-7-rc3/</link>
	<description>apparently much happier in person</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:03:04 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: D'Arcy</title>
		<link>http://www.darcynorman.net/2006/04/15/drupal-4-7-rc3/#comment-81691</link>
		<dc:creator>D'Arcy</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-81691</guid>
		<description>I was thinking of doing that, but several of the modules are taken directly out of Drupal&#039;s CVS repository, and I didn&#039;t want to have any conflicts. Regardless, I may check our distro into our SVN repository for backup and change tracking...</description>
		<content:encoded><![CDATA[<p>I was thinking of doing that, but several of the modules are taken directly out of Drupal&#8217;s CVS repository, and I didn&#8217;t want to have any conflicts. Regardless, I may check our distro into our SVN repository for backup and change tracking&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D'Arcy</title>
		<link>http://www.darcynorman.net/2006/04/15/drupal-4-7-rc3/#comment-81692</link>
		<dc:creator>D'Arcy</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-81692</guid>
		<description>Sami, the SVN technique will also make it easier to stage deployments - can test an update on my desktop easily, commit anything that works, then just svn update on the server to pick up changes. Makes sense. Our Drupal deployment is now in SVN and I&#039;ll try to not edit files directly on the server anymore :-)

The one thing that will get weird is the files directory - don&#039;t want those going into svn, but it will be tricky because they&#039;ll keep showing up in svn status. Must resist &quot;svn add *&quot; :-)</description>
		<content:encoded><![CDATA[<p>Sami, the SVN technique will also make it easier to stage deployments &#8211; can test an update on my desktop easily, commit anything that works, then just svn update on the server to pick up changes. Makes sense. Our Drupal deployment is now in SVN and I&#8217;ll try to not edit files directly on the server anymore <img src='http://www.darcynorman.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>The one thing that will get weird is the files directory &#8211; don&#8217;t want those going into svn, but it will be tricky because they&#8217;ll keep showing up in svn status. Must resist &#8220;svn add *&#8221; <img src='http://www.darcynorman.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sami Khan</title>
		<link>http://www.darcynorman.net/2006/04/15/drupal-4-7-rc3/#comment-81693</link>
		<dc:creator>Sami Khan</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-81693</guid>
		<description>A lot of guys say to make things even easier you might want to load Drupal into SVN and then do an export or checkout from that. That way if you hack your code, you&#039;ll know what changes you made, etc.</description>
		<content:encoded><![CDATA[<p>A lot of guys say to make things even easier you might want to load Drupal into SVN and then do an export or checkout from that. That way if you hack your code, you&#8217;ll know what changes you made, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
