Daniel Baston <dbas...@gmail.com> writes: > I would suggest that we should only commit to stable branches for the > purpose of fixing a bug. No, we don't promise a stable API, so it may arise > that we need/want to change the API in a micro release to accomodate a > bugfix, though we still should try to avoid it (and generally have, I > think.)
I agree, and would say there should be a real focus on stability, so bugfixes only as Daniel says, plus doc improvements. Packaging systems update to new micro releases. The social contract is that such updates are nearly 100% safe, and are just bugfixes. Once you change that, even if a micro in name, it isn't really a micro.
