This week, I took a vacation for the first time in 6 months, and coincidentally this will also be my first blog post about IMmerge in 6 months. During some downtime on the plane, I decided to whip out my laptop and figure out what is needed to get IMmerge finished. There’s nothing quite like breaking your daily routine to get you kickstarted on some new (or old) projects!
Interesting stats:
Last sync to IMmerge source code repository: Sun Mar 21 16:30:26 CST 2010
Last IMmerge-related blog post: January 11, 2010
So here is the current status. IMmerge 1.0 uses a new merge engine, so much of the code had to be rewritten; I am satisfied that all old features in 0.66 are working in the new 1.0 engine. Next, I will release a public beta of IMmerge 1.0, which will include the GUI, and Trillian LOG-XML interconversion, but no other new features. Before I release this, the following issues must be fixed:
- TrLogReader: multiple blank lines are collapsed into one
- TrLogReader: fails to parse message timestamp containing seconds
The following feature needs to be implemented:
- TrLogReader: does not distinguish between incoming/outgoing messages yet
The first 2 issues can be fixed quickly, while the 3rd (feature) will take some time. Note that all the issues deal with TrLogReader parsing, which is only used when a session in Trillian .LOG needs to be converted into some other format (currently only XML possible)
Question: Would you rather wait until the incoming/outgoing feature is finished, or is it acceptable to skip it for the first beta?
![[RSS]](http://zalbee.intricus.net/immerge/blog/wp-includes/images/rss.png)
using a supported browser (such as Firefox) to get a newsfeed for this blog. You can then subscribe and the newsfeed will automatically update when a new post is made. You can also add the RSS URL:
