Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Cadence #732

Open
jasonbosco opened this issue Sep 22, 2022 · 0 comments
Open

Release Cadence #732

jasonbosco opened this issue Sep 22, 2022 · 0 comments

Comments

@jasonbosco
Copy link
Member

jasonbosco commented Sep 22, 2022

We tend to add features and fixes on a continuous iterative cycle and publish RC (Release Candidate) builds every 1-2 weeks. Once the amount of changes have reached a critical mass, we then go into a feature freeze for the upcoming version, address a final round of last-mile issues if any, run performance benchmarks and regression tests, continuously dogfood the builds and if everything looks good we do a final GA (Generally Available) release.

We do not have a fixed timeline for GA releases since we want final builds to be sufficiently tested and stable. That said, in the past we've done GA releases every 2-3 months.

@jasonbosco jasonbosco changed the title ### Our Release Cadence Release Cadence Sep 22, 2022
@typesense typesense locked and limited conversation to collaborators Sep 22, 2022
@jasonbosco jasonbosco pinned this issue Sep 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant