Hi all,
With 0.23.0 out and 0.24.0 in active development, I'd like to open a discussion on whether the next release should be tagged 1.0.0 instead of continuing the 0.x line. A few reasons it feels overdue: 1. Maturity. Thrift has been a top-level Apache project since 2010. The wire protocol, IDL, and language libraries are stable in practice — downstream users already treat them as 1.x. 2. Mixed signals. composer.json for the PHP library already declares "dev-master": "1.0.x-dev" via branch-alias, so part of the project is preparing for 1.0 internally — but releases keep going out as 0.x. 3. Semver mismatch. Per semver, 0.x means "anything may change at any time." That no longer matches reality. Tagging 1.0.0 is the standard way to communicate "production-ready, semver compatibility going forward." 4. A natural cut-off. Several in-flight breaking changes (e.g. THRIFT-5956 raising PHP's minimum to 8.1) are easier to communicate as a 1.0.0 transition than as another 0.x bump. A few questions: - Is there a deliberate reason we are still on 0.x — a specific blocker, or just inertia? - Should the next release simply be tagged 1.0.0, or do we ship 0.24.0 first and 1.0.0 separately afterwards? - Anything in downstream tooling that would break with a major-version jump? Thanks, Volodymyr Panivko
