“When will the next version of Ryuzine be released?”
This is a question that has come up a couple of times recently, especially from those who’ve noted that none of the files on GitHub have been updated since August or September of 2015.
Well, the simple answer is, “when it’s necessary.”
We don’t follow the software development idea of “release early, release often.” Ryuzine updates have historically been driven by updates to the web browsers in which it runs, either to fix something the browser update broke or to take advantage of a new browser feature. Since the release of Ryuzine 1.0 we haven’t become aware of any browser updates breaking the webapps, nor have any “killer” features been introduced that we think Ryuzine should take advantage of.
Furthermore, Ryuzine 1.0 heavily modularized the webapps, with more formerly integrated features now made optional in add-ons. The flexibility of the Add-Ons API would allow the webapps to utilize new browser features without requiring the core code to be updated.
In conclusion: If it ain’t broke, don’t fix it. 😉