<?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: Outlook causes mini Y2k</title>
	<atom:link href="http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/</link>
	<description>The calendar guru!</description>
	<lastBuildDate>Wed, 04 Nov 2009 18:48:34 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Outlook 2007 Feature Feedback at 16cards</title>
		<link>http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/comment-page-1/#comment-1166</link>
		<dc:creator>Outlook 2007 Feature Feedback at 16cards</dc:creator>
		<pubDate>Sun, 18 Mar 2007 04:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/#comment-1166</guid>
		<description>[...] http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/&#160;(In the summer of 2005, I was quite grave about the Daylight Saving Time change. I identified that the largest pain point would be that meetings scheduled during the&#160;overlap between new DST start&#160;[early March] and old [early April]&#160;on a system prior to having the operating system patched with new DST information. My claim was that users would see this as Outlook being fragile and that we should prepare. See next link&#8230;) [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/&nbsp;(In" rel="nofollow">http://www.calendarreview.com/2007/02/15/outlook-causes-mini-y2k/&nbsp;(In</a> the summer of 2005, I was quite grave about the Daylight Saving Time change. I identified that the largest pain point would be that meetings scheduled during the&nbsp;overlap between new DST start&nbsp;[early March] and old [early April]&nbsp;on a system prior to having the operating system patched with new DST information. My claim was that users would see this as Outlook being fragile and that we should prepare. See next link&#8230;) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
