<?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: Launching Boxxet</title>
	<atom:link href="http://blog.boxxet.com/launching-boxxet-2007-01-15/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.boxxet.com/launching-boxxet-2007-01-15/</link>
	<description>News and updates for Boxxet</description>
	<lastBuildDate>Wed, 09 Jul 2008 14:42:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Boxxet Blog &#187; Metrics of a Closed Beta: Losing 3/4 of Potential Users</title>
		<link>http://blog.boxxet.com/launching-boxxet-2007-01-15/comment-page-1/#comment-1014</link>
		<dc:creator>The Boxxet Blog &#187; Metrics of a Closed Beta: Losing 3/4 of Potential Users</dc:creator>
		<pubDate>Mon, 12 Feb 2007 13:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxxet.com/launching-boxxet-2007-01-16/#comment-1014</guid>
		<description>[...] Boxxet spent a long time in a closed beta, longer than we expected. Some reasons were normal: stamping out bugs, making sure the application scales, and determining weak areas that need improvement or protection. More importantly, after our first wave of users of the closed beta, we felt that we needed to add more automation to the system. [...]</description>
		<content:encoded><![CDATA[<p>[...] Boxxet spent a long time in a closed beta, longer than we expected. Some reasons were normal: stamping out bugs, making sure the application scales, and determining weak areas that need improvement or protection. More importantly, after our first wave of users of the closed beta, we felt that we needed to add more automation to the system. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
