<?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: Explanation of snapshot file name dates</title>
	<atom:link href="http://blog.pfsense.org/?feed=rss2&#038;p=119" rel="self" type="application/rss+xml" />
	<link>http://blog.pfsense.org/?p=119</link>
	<description>News, reviews and more related to the pfSense firewall project</description>
	<lastBuildDate>Fri, 17 May 2013 19:48:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Christopher</title>
		<link>http://blog.pfsense.org/?p=119&#038;cpage=1#comment-162</link>
		<dc:creator>Christopher</dc:creator>
		<pubDate>Tue, 24 Jul 2007 08:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=119#comment-162</guid>
		<description><![CDATA[I am still not convinced that this naming scheme is the best option. Aside from the format issue, which just adds another favor.&lt;br/&gt;&lt;br/&gt;If there would be a unique build number in the name all confusion could go away. It gets increased (automatically) whenever a change to the CVS tree has been committed. Otherwise the snapshot server just rebuilds with the same number but maybe a new file date.]]></description>
		<content:encoded><![CDATA[<p>I am still not convinced that this naming scheme is the best option. Aside from the format issue, which just adds another favor.</p>
<p>If there would be a unique build number in the name all confusion could go away. It gets increased (automatically) whenever a change to the CVS tree has been committed. Otherwise the snapshot server just rebuilds with the same number but maybe a new file date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin</title>
		<link>http://blog.pfsense.org/?p=119&#038;cpage=1#comment-134</link>
		<dc:creator>Colin</dc:creator>
		<pubDate>Sun, 01 Jul 2007 15:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=119#comment-134</guid>
		<description><![CDATA[I second this, the majority of developers may be US-based, but the majority of users are probably not.]]></description>
		<content:encoded><![CDATA[<p>I second this, the majority of developers may be US-based, but the majority of users are probably not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rupert</title>
		<link>http://blog.pfsense.org/?p=119&#038;cpage=1#comment-132</link>
		<dc:creator>Rupert</dc:creator>
		<pubDate>Fri, 29 Jun 2007 08:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=119#comment-132</guid>
		<description><![CDATA[I live in the UK but work on both sides of the pond, so this is a common issue for the first 12 days of every month! &lt;br/&gt;&lt;br/&gt;These days I use YYYY-MM-DD for all dates. It removes confusion regardless of which way around you normally write months and days. Added bonus is looking at a directory full of files starting pfSense-YYYY-MM-DD.* will all be shown in date order if I&#039;m sorting alphabetically.&lt;br/&gt;&lt;br/&gt;I normally rename my downloads to add dates anyway, but developers might like to consider switching date formats for universal appeal.&lt;br/&gt;&lt;br/&gt;Thanks for all the hard work!&lt;br/&gt;&lt;br/&gt;Rupert]]></description>
		<content:encoded><![CDATA[<p>I live in the UK but work on both sides of the pond, so this is a common issue for the first 12 days of every month! </p>
<p>These days I use YYYY-MM-DD for all dates. It removes confusion regardless of which way around you normally write months and days. Added bonus is looking at a directory full of files starting pfSense-YYYY-MM-DD.* will all be shown in date order if I&#8217;m sorting alphabetically.</p>
<p>I normally rename my downloads to add dates anyway, but developers might like to consider switching date formats for universal appeal.</p>
<p>Thanks for all the hard work!</p>
<p>Rupert</p>
]]></content:encoded>
	</item>
</channel>
</rss>
