<?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: Family Tree Maintenance Saturday (5th June from 7-8am GMT)</title>
	<atom:link href="http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/</link>
	<description>The official Ancestry.co.uk blog</description>
	<lastBuildDate>Wed, 24 Apr 2013 18:23:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: golflimatangoancestry</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-299</link>
		<dc:creator>golflimatangoancestry</dc:creator>
		<pubDate>Wed, 09 Jun 2010 11:52:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-299</guid>
		<description>Not much point in communicating these things if you give us the wrong time!</description>
		<content:encoded><![CDATA[<p>Not much point in communicating these things if you give us the wrong time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akeck</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-298</link>
		<dc:creator>Akeck</dc:creator>
		<pubDate>Tue, 08 Jun 2010 18:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-298</guid>
		<description>We do apologize for the inconvenience.  The reason we communicate these things through the blog is that it is the fastest and easiest way to get you up to date information. A banner should also appear on your logged in homepage letting you know about any planned site maintenance work but if you do not see this then please let us know. You can also contact our Member Services team on 0800 404 97 23 if you would like to speak to someone directly with any questions or concerns you may have. </description>
		<content:encoded><![CDATA[<p>We do apologize for the inconvenience.  The reason we communicate these things through the blog is that it is the fastest and easiest way to get you up to date information. A banner should also appear on your logged in homepage letting you know about any planned site maintenance work but if you do not see this then please let us know. You can also contact our Member Services team on 0800 404 97 23 if you would like to speak to someone directly with any questions or concerns you may have. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-297</link>
		<dc:creator>Sue</dc:creator>
		<pubDate>Tue, 08 Jun 2010 08:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-297</guid>
		<description>It would be nice to know what is going on!!!!!  I haven&#039;t been able to access any records on Ancestry for over 12 hours.  Is there a problem? Are Ancestry undertaking maintenance?

We pay money to access these records why can&#039;t Ancestry provide a better level of customer service and place a prominent message on the front page whenever there is a problem or planned maintenance.  Most people will understand provided they know what is happening.</description>
		<content:encoded><![CDATA[<p>It would be nice to know what is going on!!!!!  I haven&#8217;t been able to access any records on Ancestry for over 12 hours.  Is there a problem? Are Ancestry undertaking maintenance?</p>
<p>We pay money to access these records why can&#8217;t Ancestry provide a better level of customer service and place a prominent message on the front page whenever there is a problem or planned maintenance.  Most people will understand provided they know what is happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Annie</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-296</link>
		<dc:creator>Annie</dc:creator>
		<pubDate>Tue, 08 Jun 2010 08:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-296</guid>
		<description>Are the powers-that-be working on unpublicised maintenance.  Since last night my Ancestry pages have gone on a go-slow.  Its taking ages for page updates.  Its not happening on any of my other websites so I assume its a prob with Ancestry.</description>
		<content:encoded><![CDATA[<p>Are the powers-that-be working on unpublicised maintenance.  Since last night my Ancestry pages have gone on a go-slow.  Its taking ages for page updates.  Its not happening on any of my other websites so I assume its a prob with Ancestry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: poppytod</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-295</link>
		<dc:creator>poppytod</dc:creator>
		<pubDate>Mon, 07 Jun 2010 23:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-295</guid>
		<description>I do not normally read Blogs, only read this by mistake. I agree with other comments, I would never know of this maintanance, BETTER TO PUT IT ON &quot;HOME PAGE&quot;!!! Nothing worse than being thrown out halfway through a search.</description>
		<content:encoded><![CDATA[<p>I do not normally read Blogs, only read this by mistake. I agree with other comments, I would never know of this maintanance, BETTER TO PUT IT ON &#8220;HOME PAGE&#8221;!!! Nothing worse than being thrown out halfway through a search.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-291</link>
		<dc:creator>Carol</dc:creator>
		<pubDate>Sat, 05 Jun 2010 06:59:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-291</guid>
		<description>AGAIN!!!!!!!!!!!
OMG, it&#039;s Saturday morning and I got up early to get stuck in with my research and update my tree!!!
Yes you are right, some prior warning would have been much appreciated. I could have had a lie in!
AGHhhhhhhhhhhhhhhhhhh!</description>
		<content:encoded><![CDATA[<p>AGAIN!!!!!!!!!!!<br />
OMG, it&#8217;s Saturday morning and I got up early to get stuck in with my research and update my tree!!!<br />
Yes you are right, some prior warning would have been much appreciated. I could have had a lie in!<br />
AGHhhhhhhhhhhhhhhhhhh!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave O'Donoghue</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-290</link>
		<dc:creator>Dave O'Donoghue</dc:creator>
		<pubDate>Sat, 05 Jun 2010 06:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-290</guid>
		<description>Yet asgain we have been let down with a lack of communication. Why do I have to read the Blog to find out when and why the service would be down?</description>
		<content:encoded><![CDATA[<p>Yet asgain we have been let down with a lack of communication. Why do I have to read the Blog to find out when and why the service would be down?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: golflimatangoancestry</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-289</link>
		<dc:creator>golflimatangoancestry</dc:creator>
		<pubDate>Sat, 05 Jun 2010 06:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-289</guid>
		<description>Sorry that should have read 07:45 BST</description>
		<content:encoded><![CDATA[<p>Sorry that should have read 07:45 BST</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: golflimatangoancestry</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-288</link>
		<dc:creator>golflimatangoancestry</dc:creator>
		<pubDate>Sat, 05 Jun 2010 06:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-288</guid>
		<description>Not only is this information hidden away it also appears to be completely inaccurate.  It is now 07:30 BST which is 06:45 GMT and the system is down before the stated time.  Does the notice mean 07:00 to 08:00 GMT (as stated) or 07:00 to 08:00 BST  or don&#039;t they know the difference??</description>
		<content:encoded><![CDATA[<p>Not only is this information hidden away it also appears to be completely inaccurate.  It is now 07:30 BST which is 06:45 GMT and the system is down before the stated time.  Does the notice mean 07:00 to 08:00 GMT (as stated) or 07:00 to 08:00 BST  or don&#8217;t they know the difference??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mimi Malin</title>
		<link>http://blogs.ancestry.com/uk/2010/06/04/family-tree-maintenance-saturday-5th-june-from-7-8am-gmt/#comment-287</link>
		<dc:creator>Mimi Malin</dc:creator>
		<pubDate>Sat, 05 Jun 2010 06:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=730#comment-287</guid>
		<description>I agree, why wasn&#039;t this put on the home page so we had decent warning ?</description>
		<content:encoded><![CDATA[<p>I agree, why wasn&#8217;t this put on the home page so we had decent warning ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
