V6.3-000A brings timely fixes to issues, including two issues in the string optimization introduced in V6.3-000, GTM-8540 and GTM-8549. The release includes other fixes and performance enhancements, as described in the release notes (http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.3-000_Release_Notes.html). Please do use V6.3-000A.
While not a part of the GT.M distribution, we would also like to let you know about a reference implementation of GT.M Peer Replication, a type of bi-directional replication that uses GT.M triggers. Subsets of application logic which do not need update / transaction serialization, but which can benefit by aggregating updates from separate instances, can be deployed using peer replication. For example, financial transactions on a bank account must be serialized because each transaction depends on the result of the previous transaction on that account; balance inquiries need not be serialized because, while an inquiry to an account depends on the last financial transaction on that account, it does not depend on the last inquiry to that account. The reference implementation of GT.M peer replication is available as a plugin that you can add to your application (the reference implementation of a plugin is code that you can use as-is if it meets your needs, or adapt to your needs as appropriate; an existing example is the POSIX plugin). Plugins are not part of the GT.M core release but are separately released packages. The plugin includes a detailed readme file on implementing peer replication using the plugin.