As reported last week, the next stable release of MySource Matrix (3.6.0) has been pushed back a month in order to test some new performance improvements in both PostgreSQL and Oracle. The next release candidate (3.6.0 RC2) will be released on Monday along with 3.4.5 stable.
Several changes have been made to MySource Matrix this week to help with system performance and caching. Due to the importance of these features to clients, they have been made to both 3.6.0 RC1 and 3.7.0 development. Being so close to the scheduled release of 3.6.0 stable, we have decided to postpone the stable release for another month and release another release candidate (3.6.0 RC2). This will allow for additional testing of these changes to ensure they are indeed working correctly in production systems.
Some more changes have been made to My Source Matrix for what we hope is a permanent fix for the treeid problems we've been having recently with database systems have been set to a specific collating order (which can't be changed after initdb is run on the system). Basically it involves changing the treeid field from a varchar to a binary string type (bytea). These fields sort based on byte (read: ASCII) values, a critical feature of the treeid field's operation. This would also eliminate any problems still seen after the temporary changes where some characters are considered "equal" and thus ignored in the sort order.
New versions of MySource Matrix were released on the web site this week, the first in 3 months. A big thank you to all the developers for the huge number of bugs that managed to get fixed Monday morning and to Marcus for helping with the release.
A new release candidate of MySource Matrix will be released on Monday. Version 3.6.0 RC1 will mark the end of the new stable feature set and no new features will be added to the 3.6.x branch from this point onward. This will allow us to move steadily toward a new stable release in either August or September, pending beta testing and bug fixing.