<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Eitan Suez's Home: Finally, a new release..Ashkelon v0.9</title>
    <link>http://www.u2d.com/articles/2006/02/04/finally-a-new-release-ashkelon-v0-9</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Finally, a new release..Ashkelon v0.9</title>
      <description>&lt;p&gt;Over the last year, here and there when I've had an idea or a little time I've
changed something or added a feature to ashkelon.  Much time has passed and 
I hadn't cut a release.  For a while I really wanted to finish idea x or
feature y "before making another release."&lt;/p&gt;

&lt;p&gt;That was a bad idea.  Yesterday I decided that was enough.  It'd been way
too long since I'd last published a release.  I spent a few hours updating
the documentation, testing the release, updating the documentation again,
testing the release again until I was satisfied.&lt;/p&gt;

&lt;p&gt;Finally, &lt;a href="http://ashkelon.sourceforge.net/"&gt;version 0.9 is out&lt;/a&gt;.
Sure, a number of features are only half
finished, but at least others can play with them.  I mean they've been
in CVS for a while.  But few bother to get that close to a project,
I admit.&lt;/p&gt;

&lt;p&gt;Just because I'm not spending much time developing ashkelon does not mean
that I'm not using it.  For my purposes, ashkelon has been feature complete
since 2001, since before I even considered open-sourcing it.&lt;/p&gt;

&lt;p&gt;I use it on a regular basis when I code and have
been doing so for five years now.  That's an awful long time.  People
should know when to give up.  I think this five-year mark is a sign that
if this tool has not gotten any traction by now, it probably never 
will.&lt;/p&gt;

&lt;p&gt;What saddens me the most is that even the idea itself has met failure.
As far as I know people are ignorant of the idea, the notion that a better
system for api documentation is a database application.  In the ruby
world we've yet to see rdoc implemented as a rails app.  Maybe some
day someone will write one.&lt;/p&gt;</description>
      <pubDate>Sat, 04 Feb 2006 11:16:00 -0600</pubDate>
      <guid isPermaLink="false">urn:uuid:f9986a6deddca3875e90c553865724a9</guid>
      <author>Eitan</author>
      <link>http://www.u2d.com/articles/2006/02/04/finally-a-new-release-ashkelon-v0-9</link>
    </item>
  </channel>
</rss>

