Closed taiki-e closed 7 months ago
I think having explicit mention of it in CONTRIBUTING.md (or even any documentation about the branching/backporting policy at all) would be a good start. I explicitly looked for some, didn't find any, found that HEAD pointed at 0.4, and figured I should target my bugfix to the release branch.
In other words, it wasn't exactly an accident: it was my genuine best guess at how to get a bugfix merged into a previous release line in the absence of documentation, given that I was uncertain that a fix to master would get cherry-picked to a release branch.
cc @Kobzol: Are there any options for doing this in rust-lang/team or somewhere? I was going to refer to what rust-lang/rust does in rust-lang/team, but rust.toml doesn't seem to exist in the dierctry that futures-rs.toml exist, so I'm not sure what to do.
This would help avoid problems like https://github.com/rust-lang/futures-rs/pull/2801#issuecomment-1819252187.
rust-lang/rust already has a mechanism for this (https://github.com/rust-lang/rust/pull/118607#issuecomment-1838839291), but I don't know how to enable it for this repo.