PRESS RELEASE: 02/29/08
The Concordance developers are excited to bring you the 0.13 release. This release brings a slew of bug fixes, code cleanup, and a few minor feature updates. It is recommended that all users upgrade.

In addition, we'd like to announce two major changes to the project.

PROJECT RENAME
Effective immediately we will begin the process of renaming our project to Concordance. Version 0.13 is the last version released under the harmony or harmonycontrol name. All future versions will be released under the Concordance name. The next version is expected to be called 0.20.

We feel the new name will better respect any trademarks and prevent any confusion between our project and Logitech's software. This will also make it easier for people to package and distribute our software. In addition, it gives us a unique name and presence.

Between now and the next release, the website will be in transition so you may see both names.

LIBRARY SPLIT
In addition to renaming the project, all future versions of Concordance will be split between a shared library, libconcord, and a UI, concordance. The majority if this work is already done in CVS and will be merged and finalized for the next release (most likely called 0.20).

Libconcord encapsulates all of the work to talk to, read from, and write to the various remotes and devices we support and exports an easy-to-use C API. The library will be cross-platform (in CVS it already works on Mac OS X, Linux, and Windows), and we plan to provide bindings for a variety of higher-level languages. Having a separate library with a clean API will allow user-interfaces to be written by anyone. This means it becomes simple for someone to write a platform-native UI that works best for that platform without having to worry about the details of interacting with the device. We believe this will allow a variety of UIs that best serve end-users.

Concordance is a cross-platform CLI interface that utilizes libconcord. Concordance will look and feel exactly like previous versions of our software did - and in fact, it's the UI code split out from the older code. In addition to an official, simple, and default user-interface, it will also serve as a test-driver for the library.

PLANNING FOR THE CHANGES
Packagers should plan for having to split their package into two separate packages as well as any transitional packages required to make the rename smooth for their users. If you are unsure of how to do this, you may want to look at how your distribution handled the rename of the Gaim project to Pidgin.