ansible/changelogs/fragments/deprecate-by-date.yml

minor_changes:
- "Ansible now allows deprecation by date instead of deprecation by version. This is possible for plugins and modules (``meta/runtime.yml`` and ``deprecated.removed_at_date`` in ``DOCUMENTATION``, instead of ``deprecated.removed_in``), for plugin options (``deprecated.date`` instead of ``deprecated.version`` in ``DOCUMENTATION``), for module options (``removed_at_date`` instead of ``removed_in_version`` in argument spec), and for module option aliases (``deprecated_aliases.date`` instead of ``deprecated_aliases.version`` in argument spec)."
Deprecate module in collection: allow removal date in documentation, make validate-modules ensure version and date match (#69727) * Allow to deprecate module by date in documentation. * Make sure deprecation date/version match between module docs and meta/runtime.yml. * Unrelated fix: don't compare deprecated module version to Ansible's version in collection. * Allow documentation's removal version to be something else than fixed list of Ansible versions for collections. * Linting. * Allow to deprecate plugin options by date. * Add changelog fragment for deprecation by date (also covers #68177). 2020-05-28 23:20:52 +02:00			`minor_changes:`
			- "Ansible now allows deprecation by date instead of deprecation by version. This is possible for plugins and modules (``meta/runtime.yml`` and ``deprecated.removed_at_date`` in ``DOCUMENTATION``, instead of ``deprecated.removed_in``), for plugin options (``deprecated.date`` instead of ``deprecated.version`` in ``DOCUMENTATION``), for module options (``removed_at_date`` instead of ``removed_in_version`` in argument spec), and for module option aliases (``deprecated_aliases.date`` instead of ``deprecated_aliases.version`` in argument spec)."