STK/Unit 1.0 Release Candidate 4 is out!
STK/Unit 1.0 Release Candidate 4 should be a stable version. STK/Unit main author uses the software since 2010, but heavily recoded when he decided to make it public. All old tests he wrote still work, and there are no open bugs.
Since the first public release, rc1, we only received some private feedback. That has been valuable, because helped us to identify bugs and flaws. But we really wish to receive some public feedback before claiming STK/Unit production-ready.
This Release Candidate was not planned. We are releasing it because we fixed a bug in the configuration routines, and we want to reduce access to tables, add some tests and store version information in a database called meta_info. If more non-trivial bugs are reported, we will release another RC, but it is very unlikely. Next STK/Unit release will probably be the first stable version!
STK/Unit supports the following platforms:
- MariaDB 10.0, 5.5
- MariaDB 5.1, 5.2, 5.3 (with some documented issues: a few DDL-specific assert functions could generate obscure exceptions)
- MySQL 5.6, 5.5
- MySQL 5.1 (with same problems MariaDB 5.1 has)
Here is a complete list of changes in 1.0 Release Candidate 4:
- Fix: #1174710
- During installation, server bahavior is now strict
- Make sure that AUTO_CLEAN works if foreign_key_checks is off (rare!)
- BTs are now executed alphabetically, not in undefined order
- Often read options are now cached
- Some table options for better Aria integrity and MEMORY performance
- added ts() and tc() (was a trivial feature request)
- show_* routines
Documentation and Downloads for STK/Unit and others STK tools to come, are avaible from here:
The public Mailing List can be found here:
The STK team encourages you to try STK/Unit in your databases, report any bugs you may find, ask for help in the list when needed, and let us know any comments. Your feedback is valuable for us!
The STK Team