Patrick Steinhardt <ps@xxxxxx> writes: > +The intent of this document is to track upcoming deprecations for the next > +major Git release. Furthermore, this document also tracks what will _not_ be > +deprecated. This is done such that the outcome of discussions documente both > +when the discussion favors deprecation, but also when it rejects a deprecation. "next major Git release" -> "future breaking release(s)". I do not know offhand if we want to plan for longer timespans that may cover multiple breaking releases, hence (s) in parentheses. "documente" -> "document". > +This is a living document as the environment surrounding the project changes > +over time. An earlier decision to deprecate or change something may need to be > +revisited from time to time. So do not take items on this list to mean "it is > +settled, do not waste our time bringing it up again". But you are expected to be aware of past discussion, and if you are not bringing anything new to the table, you are wasting our time. Note that pointing out an old rationale no longer applies to today's world still counts as a new datapoint in a renewed discussion.
