<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Resurrecting XPlanner</title>
	<atom:link href="http://blog.code-adept.com/2008/08/07/resurrecting-xplanner/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.code-adept.com/2008/08/07/resurrecting-xplanner/</link>
	<description>Random thoughts on Agile development and other things geeky.</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:00:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Simon</title>
		<link>http://blog.code-adept.com/2008/08/07/resurrecting-xplanner/#comment-264</link>
		<dc:creator><![CDATA[Simon]]></dc:creator>
		<pubDate>Tue, 17 Feb 2009 13:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://codeadept.wordpress.com/?p=54#comment-264</guid>
		<description><![CDATA[I am a big fan of this tool, and use it on a daily basis. Please keep me posted!]]></description>
		<content:encoded><![CDATA[<p>I am a big fan of this tool, and use it on a daily basis. Please keep me posted!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curtis</title>
		<link>http://blog.code-adept.com/2008/08/07/resurrecting-xplanner/#comment-58</link>
		<dc:creator><![CDATA[Curtis]]></dc:creator>
		<pubDate>Wed, 15 Oct 2008 00:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://codeadept.wordpress.com/?p=54#comment-58</guid>
		<description><![CDATA[Chomping at the bits to see the next release of XPlanner.  Although, I&#039;m no longer a developer, I would like to contribute in some way.]]></description>
		<content:encoded><![CDATA[<p>Chomping at the bits to see the next release of XPlanner.  Although, I&#8217;m no longer a developer, I would like to contribute in some way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Anderson</title>
		<link>http://blog.code-adept.com/2008/08/07/resurrecting-xplanner/#comment-55</link>
		<dc:creator><![CDATA[Jeremy Anderson]]></dc:creator>
		<pubDate>Tue, 26 Aug 2008 13:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://codeadept.wordpress.com/?p=54#comment-55</guid>
		<description><![CDATA[I&#039;m still trying to work out the particulars right now.  My first priority of course is what needs to be done for the book.  Once that is done, there are a few different directions that I&#039;m kicking around right now.

	*Do some major refactoring of the user interface
	*Add some features such as the ability to use story points
	*Make some changes to the underlying object model and database to allow for importing projects from other XPlanner instances
	*Possible Rails/Grails re-write???

One of the first priorities is that as I understand it, there is a problem with users upgrading from 0.6.x to 0.7.x, so I have started some work on migration scripts to hopefully allow users to export their existing data from 0.6.2 to XML so that they can then import it into a version 0.7.x and newer database.  My biggest decision right now revolves around how much new development to do in the existing project because if I&#039;m just going to end up doing a Rails/Grails re-write, it wouldn&#039;t make much sense to exert a lot of effort on new features in the existing code base.  Fixing some critical bugs in the existing code base and figuring out the direction of the project is where I&#039;m at now.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m still trying to work out the particulars right now.  My first priority of course is what needs to be done for the book.  Once that is done, there are a few different directions that I&#8217;m kicking around right now.</p>
<p>	*Do some major refactoring of the user interface<br />
	*Add some features such as the ability to use story points<br />
	*Make some changes to the underlying object model and database to allow for importing projects from other XPlanner instances<br />
	*Possible Rails/Grails re-write???</p>
<p>One of the first priorities is that as I understand it, there is a problem with users upgrading from 0.6.x to 0.7.x, so I have started some work on migration scripts to hopefully allow users to export their existing data from 0.6.2 to XML so that they can then import it into a version 0.7.x and newer database.  My biggest decision right now revolves around how much new development to do in the existing project because if I&#8217;m just going to end up doing a Rails/Grails re-write, it wouldn&#8217;t make much sense to exert a lot of effort on new features in the existing code base.  Fixing some critical bugs in the existing code base and figuring out the direction of the project is where I&#8217;m at now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mammut</title>
		<link>http://blog.code-adept.com/2008/08/07/resurrecting-xplanner/#comment-48</link>
		<dc:creator><![CDATA[Mammut]]></dc:creator>
		<pubDate>Wed, 20 Aug 2008 09:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://codeadept.wordpress.com/?p=54#comment-48</guid>
		<description><![CDATA[Hey Jeremy!

Great to hear that Xplanner is alive again, can you give us a roadmap about your plans for XPlanner?]]></description>
		<content:encoded><![CDATA[<p>Hey Jeremy!</p>
<p>Great to hear that Xplanner is alive again, can you give us a roadmap about your plans for XPlanner?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

