ng0 <contact....@cryptolab.net> writes: > I want an formal, publicly tracked (not *just* on the mailinglist) RFC (like > in Rust or similar projects) procedure for all things which > can break currently existing configurations. Introducing these changes would > require to document properly what needs to changed so that people can read > about how to fix the mistakes.
[…] API changes are usually explained in the release announcement’s changelog. This doesn’t really help between releases, though. So, either we release more often (yay!) or we support the old APIs until the next release (boo!). -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
