{"id":4657,"date":"2017-04-01T21:45:38","date_gmt":"2017-04-02T02:45:38","guid":{"rendered":"http:\/\/www.macgenealogy.org\/?p=4657"},"modified":"2017-04-01T21:45:38","modified_gmt":"2017-04-02T02:45:38","slug":"family-tree-maker-2017-for-mac-and-windows-slight-delay","status":"publish","type":"post","link":"https:\/\/www.macgenealogy.org\/2017\/04\/01\/family-tree-maker-2017-for-mac-and-windows-slight-delay\/","title":{"rendered":"Family Tree Maker 2017 for Mac and Windows – Slight Delay"},"content":{"rendered":"

\"\" At the end of last month, it was announced that Family Tree Maker 2017 (both Mac and Windows) would possibly be shipping yesterday (March 31st)<\/a>.<\/p>\n

MacKiev, developers of FTM 2017, announced<\/a> earlier today that there would be a slight delay.<\/p>\n

There have been a lot of people who were upset\/irritated, but it’s quite clear from the updates MacKiev has posted that the issues were tied into replacing TreeSync with the new FamilySync, and from my experience with software development, they may have been the kinds of issues that were hard to find until the new service actually went live. <\/p>\n

To MacKiev’s credit, they pulled in 1,000 beta testers last night to check the problems and\/or bug fixes – they are taking this very seriously, and are not releasing FTM 2017 until the issues are resolved.<\/p>\n

People need to understand that they can’t just release FTM 2017 as it is, and then put out a patched version a few days from now – if there are issues with FamilySync, it could cause data corruption when syncing between your offline and Ancestry.com trees.<\/p>\n

Here’s the full release:<\/p>\n

\n3:30 AM UTAH TIME – APRIL 1<\/strong>
\nOur shipping review meeting ended at 2:30 am Utah Time without an agreement to release quite yet. A thousand beta testers were called into service yesterday evening, at the end of the second day of testing FamilySync live on the Ancestry servers with TreeSync disconnected.<\/p>\n

Our quality assurance staff have called for more research into issues raised in beta testing. Our engineers are in the office and are going to spend the day following the trail of the most worrying issues raised in testing yesterday. They may turn out to be nothing, but we aren’t going to release until we’re sure.<\/p>\n

In the meantime, Ancestry have agreed that existing FTM editions may continue to work until we ship That means that Ancestry hints, search, merge, maps and the Web dashboard will all keep working a few more days. We’ll be sending out an email to everyone who has pre-ordered FTM 2017 a bit later today. .We will keep this page updated with our progress.<\/p>\n

4 PM UTAH TIME – APRIL 1<\/strong>
\nWe have been working through the day today with those beta testers reporting unusual problems. While some were not issues after all, some indeed were and we have made a new build which is being tested by those same beta testers right now. If that testing is completely successful, we could technically launch tonight, though we will more likely decide to wait until Monday when we can consult with Ancestry engineers and do further live stress testing on their systems.<\/p>\n

In the meantime, all those with existing FTM editions may continue to work until we release. At this point, only syncing has been disconnected and Ancestry has agreed to temporarily maintain all other connection functions that will be replaced with FamilySync in FTM 2017. That means that Ancestry hints, search, merge, maps and the Web dashboard will all keep working until FTM 2017 is released. We’ll be sending out an update email tonight to everyone who is waiting for their copy of FTM 2017.\n<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

At the end of last month, it was announced that Family Tree Maker 2017 (both Mac and Windows) would possibly be shipping yesterday (March 31st). MacKiev, developers of FTM 2017, announced earlier today that there would be a slight delay. There have been a lot of people who were upset\/irritated, … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[42,79,45,4],"tags":[159],"_links":{"self":[{"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/posts\/4657"}],"collection":[{"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/comments?post=4657"}],"version-history":[{"count":0,"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/posts\/4657\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/media?parent=4657"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/categories?post=4657"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.macgenealogy.org\/wp-json\/wp\/v2\/tags?post=4657"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}