hasura / hasura/graphql-engine
[RFC] Release process
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
The idea is to have
1. Frequent releases: we should ship features as soon as they are done.
We can start with a bi-weekly release schedule - every 2 weeks we release new features that we are have been working on. We can tweak this as and when it is required (maybe a larger window if we are working on large features). There will always be cases where we will have to make releases outside this cycle - critical bug fixes, security fixes etc.
2. Stability: the aim is to reduce the number of cases where we need to do an immediate patch release to fix an issue.
We will have a beta channel where a release goes first, fix any issues reported by the users and then promote it as a stable release.
We can follow Rust's release process:
1. https://internals.rust-lang.org/t/release-channels-git-branching-and-the-release-process/1940
2. https://forge.rust-lang.org/release/process.html
Contributor guide
Assessment
This issue has not been assessed yet.