For the past year, the ever-growing DMDirc code base has been managed using the Git version control system. We still mirror our code to an SVN repository, and a couple of our automated tools still use the SVN version of things, but we’re slowly and surely modifying, upgrading or scrapping these in favour of Git-based solutions.

Recently we began a trial of using Gerrit to manage commits made to the main DMDirc repositories for the client and the parser. Gerrit is a code review tool, which developers submit their changes to (instead of pushing them directly to the Git repositories); other developers can then review the changes, test them, and leave feedback, before ultimately approving or rejecting the change. Only once a change has been approved is it allowed to go into the repository.

This has helped us greatly improve the quality of the code that makes it into the client. Another advantage to using Gerrit is that it now allows us to open up the repositories a bit more and allow third-party contributions with much more ease than before: it is now possible for anybody to sign up to Gerrit and begin committing to DMDirc right away! We even have a guide on our Git wiki page detailing how to do just that.

If you would like to contribute to DMDirc, either by committing (via Gerrit!) or in other ways, we suggest paying a visit to #DMDirc on either Quakenet, Freenode, OTFC, Coldfront or Chatspike! (Don’t worry: we have a system in place to link all the channels together!)

At the start of the month we quietly released DMDirc 0.6.3m2 as part of our new fixed release cycle.

DMDirc 0.6.3m2 is the second milestone release since 0.6.1, and the first release we’ve made as part of the fixed cycle. It contains a large number of bug fixes and minor improvements.

As this is the first release as part of the fixed release cycle, we weren’t used to the limited timescale between releases and as such our usual ‘quiet’ period between releases had a much larger effect than it does normally. This means that we didn’t get as many features into this release as we would have liked, but we still managed to squeeze a few in:

Textpane font settings

One of our most requested improvements – you can now set both the font name and size of the text displayed in DMDirc’s textpane. The options can be set globally, per-server or per-channel as usual.

Alternate parsers (Twitter support)

DMDirc can now support different parsers in addition to our previous IRC parser. This means better or alternative IRC parsers can be developed in the future, or we can develop parsers to interact with completely different systems. As a proof of concept, we’ve developed a Twitter parser which allows you to read your Twitter news feed and post status updates direct from DMDirc!

Configurable server names

You can now configure how DMDirc displays server names in the treeview and the titlebar. This means you can (for example) show your nickname along with the server name (useful if you often connect to the same server twice as different users), or show the network name instead of the server address (in case you use a bouncer to connect to multiple networks).

License panel

We’ve also tidied up the ‘License’ panel in the about dialog, to make it much clearer which components are covered by which license. This should make it easier for anyone interested in modifying DMDirc or reusing parts of it to see where they stand.

As we’re now committed to releasing on a fixed schedule this will be the last ‘milestone’ release, and for future releases we’ll just add to the minor version number until we’ve implemented the features targeted for the next major release. This means the next release will be 0.6.3, and any further releases before the 0.7 feature set is complete will be 0.6.4, 0.6.5, etc

As always, we welcome bug reports and feature requests on our issue tracker, irc channel or as comments on this post. We will also respond to mentions on twitter. DMDirc 0.6.3m2 continues to be supported on Linux, BSD, Solaris, OS X and Windows, as well as having a standalone Jar file for any other java-capable platforms that are not specifically supported.