I’ve got only a handful of things remaining to finish before XMICAE is ready for a test release. Some of these might not even make it in to the first testing, depending on how ready I am when June 7th rolls around. I’d hoped to make the June 7th release be a public test, but it’ll probably be 0.0.0 in my version system and include a without-warranty source release under Apache 2.0. I should be able to start a private test this weekend, and release 1.0.0 as well as open it up for public testing some time the week afterward. Here’s the stuff I have left to do:
- Some UI sidebar stuff
- Removing old test files
- Adding in rolls
- Finish switching over to prepared statements.
Of these, I think that the rolls are the lowest priority, especially if I do a 0.0.0 release. I’ve come up with a solution for them that involves allowing both in-line and separate file roll documentation, meaning that it’s entirely possible to use rolls in separate places. My hypothetical 1.1.0 includes adding in “last XMI prompt” as an appropriate roll result, allowing reusable rolls (for instance, resting and healing).
The SQL security upgrades are not necessarily going to make it into 0.0.0. I’ve been having a darned difficult time getting my prepared statements to execute in certain circumstances, even ones that appear to be called in identical situations to working ones. Once I get this working, however, I expect it to be relatively quick to finish up.
I also want to move my salt settings for password hashing into config.php. It’s only referenced two places, but if you mess it up users can’t log in, so it’s important to have it working consistently in both, and it’s also something that should be changed (in theory) for each installation of XMICAE.
Test files being removed is fairly easy. I’ll probably make them available separately, though you wouldn’t necessarily want them in a production environment.