chore: update next README.md

[ematipico]

Summary

I plan to make next the default branch here on github.

Test Plan

N/A

[arendjr]

Rather than changing the default, can’t we just create a new branch (say, maintenance-1.x) off main and then merge next?

The main advantage would be that it can stay like that going forward and we wouldn’t have a confusing default.

[ematipico]

We could, however that could be a breaking change for people that use our crates from git.

Not a biggy, just wanted to have a safe approach

[arendjr]

I don't think I've ever seen someone promise API stability for their raw Git repository 😅

But in all seriousness, I don't think should ever be an argument to create new branches or avoid refactorings in a particular branch. People who use sources directly from Git are intentionally not using any releases, so the promises we try to uphold for our releases also don't apply there.

[dyc3]

IMO, anyone using git sources without pinning to a specific commit is in for a bad time. Perhaps it would be better to have a more concrete discussion on versioning, maintenance, and branches to decide what exactly we want to do going forward.

[ematipico]

Regardless, I am not ready to merge next to main, as I am still testing knope, and there are still few bugs that aren't fixed. I can't get the artefacts published in the releases.