Bug#974728: vim-scripts: Document migration from vim-addon-manager handling to Vim's native "package" functionality

[Salvatore Bonaccorso <carnil@debian.org>]

Package: release-notes
Severity: wishlist
X-Debbugs-Cc: carnil@debian.org,jamessan@debian.org

Hi

The recent update of vim-scripts to unstable (and to be released with
bullseye) contains the following NEWS file:

----cut---------cut---------cut---------cut---------cut---------cut-----
vim-scripts (20201113) unstable; urgency=low

  The addons provided by this package are now managed by Vim's native
  "package" functionality rather than vim-addon-manager.  Please follow these
  steps to ensure a smooth upgrade:

  * Before upgrading, run "vam remove <addon>" for any addon in this package
    that has been installed with "vam install <addon>".  Adjust the command
    as necessary for system-wide installed addon.
  * After upgrading, add "packadd! <addon>" to your vimrc for any addon that
    you want to use.  The addon name can be found in the package description
    or the list of directories under /usr/share/vim-scripts.

  Using VCSCommand as an example:
  * "vam remove vcscommand" will remove the vim-addon-manager setup for the
    addon.
  * Adding "packadd! VCSCommand" to your vimrc will enable (neo)vim to find
    and use the addon.

 -- James McCoy <jamessan@debian.org>  Fri, 13 Nov 2020 22:48:17 -0500
----cut---------cut---------cut---------cut---------cut---------cut-----

Might it be worth of mentioning this in the release notes, so users
can prepare in advance to move this handling to vim's native package
functionality?

Regards,
Salvatore