Hello Everyone,
It’s the beginning of October, which means we owe you an update on osTicket 2.0.
First, the obvious: we missed our Q3 target, again! We know many of you have been eagerly waiting to get your hands on 2.0, and we’re sorry we didn’t communicate the delay sooner.
The good news is that we’re very much in the final stretch.
Over the past few months, the team has been doing a fair amount of final development, integration, and panel beating behind the scenes. As we’ve brought the different pieces of 2.0 together, we’ve continued to find areas that needed a little more work, refinement, and testing than anticipated. Rather than push something out simply to meet the Q3 date, we made the call to keep working through those items and get the codebase into better shape for public testing.
There are still a few dents to knock out, but we can finally put a more concrete date around the next step:
We plan to make the osTicket 2.0 alpha release available in mid-November.
Once it’s public, you’ll be able to follow the project, spin it up, test it, break things, and start giving us real-world feedback.
We know this release has been a long time coming, and we genuinely appreciate the patience, enthusiasm, questions, and occasional well-deserved nudge from everyone following along here.
We’re almost there. A few more revisions, and we’ll be ready to hand over what we’ve been building so you can finally get your hands on it.
Please note, we'll be following up with a blog post in the next couple of days where we’ll share a little more detail on where things currently stand, what’s already in place, and what remains to be completed ahead of the public release.
More details on what to expect from the public release will follow as we get closer to November.
Cheers.
