The way we have been doing releases does not coincide well with how we
have been utilizing our stable branch. Given that we release from
master, and that many people in the community use master on a daily
basis, it makes more sense for stable to always match the latest
released version, and for master to include unreleased changes which are
considered "stable".
For experiments, we should instead use a feature branch per experiment
until we are confident that it is ready to be merged into master.
* Add mergify config
This config includes the following rules:
- Automatically merge once a PR passes all tests and is approved.
- Automatically backport each PR from our main branch into our stable branch
* Merge all tests into one run
* Cleanup and speed up test suite
* Migrate to a docker image with dav1d
* Create CI profile with debug assertions enabled
* Use faster params for all encoders
Co-authored-by: Redzic <yusufredzic@gmail.com>
