Switching to gitflow model for a while

[alerque]

Just a heads up to other developers...

I'm going to start using the gitflow model to organize this project's branches for a while. At least to get us past the 0.15.0 release milestone. I may go back to a trunk based model after that to simplify, but I'm struggling to get anything done in the current model to move the release forward without breaking the current one. I know modern devops hotstuff considers gitflow to be a legacy model, but I've never fully embraced trunk based workflows anyway. Functionally the riir branch in #1762 is already basically a develop branch and we have a bunch of pending PRs that we could merge and test together if we just called it what it is.

The v0.14.x series of releases will continue based on the master branch until such a time as v0.15.0 is ready to release from the develop branch. Whether we do alpha/beta releases from develop is an open question. Personally I don't mind just using HEAD.

New PRs should target either master or develop depending on whether they introduce breaking changes from the current major release series.

Some package managers handle HEAD builds and need adjustment

• Arch Linux AUR -git flavors (sile-git and sile-luajit-git)
• Homebrew --HEAD
• Nix (Fix broken Nix Flake on develop branch #1865)
• Add a Docker flavor besides master?

[alerque]

If anybody is interested in helping spin up Homebrew support for the new develop branch with Rusty CLI, I need somebody that can test the brew install --HEAD from this PR: Homebrew/homebrew-core#149942. I think you'd need to checkout my branch locally, then build with: HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source sile.

[alerque]

Docker images are available with the new Rust based CLI:

$ alias sile='docker run -it --volume "$(pwd):/data" --user "$(id -u):$(id -g)" ghcr.io/sile-typesetter/sile:develop'

[alerque]

Homebrew can now install the Rusty development version of SILE using brew install sile --HEAD.