Original news post, here
Work has started documenting the Twinspire API and making it available online, which can be found here. In addition, I would like to discuss how future updates will be implemented.
Because there are many things to maintain now, including the API references, our database, uploading zip files to our servers and haxelib, as well as posting and informing you of the latest updates, Twinspire will be following a strict set of guidelines which will be necessary when adding or improving new features into the engine.
For the foreseeable future, version updates for significant changes or improvements will be made on a schedule only I have access to. Improvements and community contributions will be reviewed before the pull request is merged on Github, and will be added in the next minor version update for the following week. If significant changes are made within a week that a pull request is made, and the pull request fixes a critical bug, then the pull request will be prioritised and put into the next version update over the planned changes.
What this basically means is that critical bug fixes, either done by myself or contributors, will be implemented first. Any changes or improvements to the API that does not involve critical bugs will be set aside while critical updates are applied to the next version.
You can get the latest version of Twinspire here, or over on Haxelib. Thanks for reading!