<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Infinity Data Systems</title>
	<atom:link href="http://infinitydatasystems.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://infinitydatasystems.com</link>
	<description>The Fusion of Design and Technology</description>
	<lastBuildDate>Wed, 08 Feb 2012 01:30:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>MailForge 3 Release Date</title>
		<link>http://infinitydatasystems.com/mailforge-3-release-date/</link>
		<comments>http://infinitydatasystems.com/mailforge-3-release-date/#comments</comments>
		<pubDate>Mon, 06 Feb 2012 18:35:07 +0000</pubDate>
		<dc:creator>Matt Milano</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://infinitydatasystems.com/?p=179</guid>
		<description><![CDATA[Hi Everyone, We believe we&#8217;ve finally ironed out the bug that has prevented us from committing to a solid date for MailForge 3&#8242;s release date. As we previously stated, this bug was due to a poorly documented Apple API that relates to how we display HTML emails. Now that we have this worked out, we [...]]]></description>
			<content:encoded><![CDATA[<p>Hi Everyone,</p>
<p>We believe we&#8217;ve finally ironed out the bug that has prevented us from committing to a solid date for MailForge 3&#8242;s release date. As we previously stated, this bug was due to a poorly documented Apple API that relates to how we display HTML emails.</p>
<p>Now that we have this worked out, we will be release MailForge 3 on Monday, April 2.</p>
<p>Thank you for your patience.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://infinitydatasystems.com/mailforge-3-release-date/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Moving Forward</title>
		<link>http://infinitydatasystems.com/moving-forward/</link>
		<comments>http://infinitydatasystems.com/moving-forward/#comments</comments>
		<pubDate>Thu, 29 Sep 2011 14:48:24 +0000</pubDate>
		<dc:creator>Matt Milano</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://infinitydatasystems.com/?p=137</guid>
		<description><![CDATA[This post is to inform everyone where we&#8217;ve been, where we are and, most importantly, where we&#8217;re going. Where We&#8217;ve Been When the MailForge project (then Odysseus) first started, we felt an unnecessary need to get MailForge out ASAP. As a result, some poor decisions were made early on that have caused us a great [...]]]></description>
			<content:encoded><![CDATA[<p>This post is to inform everyone where we&#8217;ve been, where we are and, most importantly, where we&#8217;re going.</p>
<p><strong>Where We&#8217;ve Been</strong><br />
When the MailForge project (then Odysseus) first started, we felt an  unnecessary need to get MailForge out ASAP. As a result, some poor  decisions were made early on that have caused us a great deal of grief  throughout the project. As one example, we licensed closed-source code  from third-parties (yes, we realize this is the same mistake Qualcomm  made) that ended up being a hinderance to us for a long time.</p>
<p>In addition, we have struggled with performance elements that have  had profound impacts on widespread features. For example, performance  limitations with SQLite have created a slew of problems with sorting.  These performance issues were only recently overcome.</p>
<p><strong>Where We Are</strong><br />
Over the last year or two we have been working on rewriting all of the  affected portions of MailForge. Unfortunately, integrating these  rewritten and improved features into the original codebase has presented  all new challenges. This has led to the &#8220;two steps forward, one step  backward&#8221; syndrome that has plagued MailForge for some time.</p>
<p><strong>Where We&#8217;re Headed</strong><br />
As announced in other sections of the forums, we have already embarked  on a complete rewrite. This will represent a 93 &#8211; 95% rewrite of the  original codebase. As stated, we have some modules and portions of the  programs rewritten already, waiting to be plugged into an improved  framework.</p>
<p>In the course of this rewrite, our main focus will be to make sure  that each and every feature works perfectly &#8230; before we move onto the  next. To ensure this level of performance we will be releasing  incremental Alpha and Beta releases to get user feedback.</p>
<p><strong>Timeframe</strong><br />
While we absolutely will not commit to an exact date, we can say that  the rewrite will be in the &#8220;months&#8221; range. We are working as fast as  possible, and will shortly provide a detailed Roadmap. We will also  start releasing the early builds in the very near future.</p>
<p>In conclusion, we want to thank everyone for their patience. As we  stated at the beginning of this project, we are in this for the long  haul. We rely on MailForge for our internal email and look forward to  many years of development.</p>
]]></content:encoded>
			<wfw:commentRss>http://infinitydatasystems.com/moving-forward/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

