> When is the next release planned after 3.31.1? Feature (.0) releases generally come out every three months, so we should be close to the next one. > My company needs If only [there was a way][1] for a corporate entity to express its needs to the maintainers in a concrete way... :) > an official release Why? I get the point of stability, but what's wrong with backporting the specific commits in the meantime? Fossil makes it easy: ---- ```shell cd ~/src/sqlite/trunk # location of Fossil checkout of SQLite3 repo fossil merge --cherrypick d09f8c36 fossil merge --cherrypick abc473fb fossil merge --cherrypick 4a302b42c7 make -j11 && make test ``` ---- These checkin IDs come from [this post][2]. All three of these require specially-crafted SQL to exploit. If your company's product is accepting arbitrary SQL, why? [1]: https://sqlite.org/prosupport.html [2]: https://sqlite.org/forum/forumpost/6c512820c26a