#16004 will introduce a breaking change. Would it be a good idea to have a dedicated section in the changlog to reflect this?
In principle, breaking changes are highlighted by having the Changed type. Changelog sections are used for topics.
that one is very breaking, we should probably have a way to signal this
The changelog entries are ordered by types within a section, Changed appear first in entry.
Pierre-Marie Pédrot said:
that one is very breaking, we should probably have a way to signal this
The way we signal very breaking changes is in the release summary usually.
This one https://coq.github.io/doc/master/refman/changes.html#version-8-11 even had some bold text in the release summary.
Maybe instead of "changed" we could have "high impact change" and "low impact change".
Sure, but the issue with these distinctions is that you always have trouble figuring out on which side of the frontier some changes go...
I think this can be derived from the amount of effort to fix all projects in CI (size of the diff e.g.).
Last updated: Dec 07 2023 at 17:01 UTC