Ævar Arnfjörð Bjarmason <[email protected]> writes: > The plan, subject to RFC feedback is to: > > * Add a new config variable `core.version`. E.g. `core.version = > 2.14.0` With this the user can specify that they'd like > new/experimental features introduced in that version (and below), > as well as immediately getting new deprecations added in that > version as errors. > > This is similar to perl's "use v<VERSION>".
As long as this does not require very new version like v3.0.0 of Git to pretend as if the user is still running an ancient v2.14.0, it is a sensible proposal, I would think. > * Add a deprecated() function to to mark deprecated features. > * TODO: Add an experimental() function to mark experimental features. Having burned by bitter experience during v1.6.0 transition, I do welcome an attempt to make it easier to communicate deprecation plans to end-users.
