Releasing VM

* NonGNU ELPA

Current package contents of GitLab vm/main will be at NonGNU-devel in
https://elpa.nongnu.org/nongnu-devel/vm.html.

You can test installing from here by add to package-archives:

(add-to-list 'package-archives 
             '("nongnu-devel" . "https://elpa.nongnu.org/nongnu-devel/"))

Note that it takes around 12 hours for an update to be available on
NonGNU-devel.

Once release is made with a release version number (1.2.3)
in vm.el, it will become available as a NonGNU ELPA
package at https://elpa.nongnu.org/nongnu/vm.html

* use package-lint to check vm.el packages
requires package-lint
  make package-lint
or 
  M-x package-lint-current-buffer
note lint will not be clean, due to xemacs references

* release is built initial in fork
then merge to make official

* version update in these files:
- Add note about release to info/vm.texinfo @item Version ..
- NEWS
- version in configure.ac AC_INIT
- lisp/vm.el Version:
  
* test build
- make distclean
- autoconf
- ./configure
- make
- make install

* pre-release testing from repo:
changes must be committed

(package-vc-install 
  '(vm :url "file:////Users/markd/projs/emacs/vm/vm-markd"
       :lisp-dir "lisp"))

Note: as of emacs 30.2, package-vc-install doesn't generate
a correct description or commit.

* commit and tag
- tag is in the form '8.3.0'
- a branch are only made if changes are needed relative to a tag


* pre-release testing from fork:
(package-vc-install
  '(vm :url"https://gitlab.com/USER/vm.git"
       :lisp-dir "lisp"
       :branch "8.3.0"))
  
* post-release testing from main repo:
(package-vc-install
  '(vm :url"https://gitlab.com/emacs-vm/vm.git"
       :lisp-dir "lisp"
       :branch "8.3.0"))

* push and test install once available in nongnu ELPA

* update version to a snapshot of the next patch
e.g. 8.3.0 -> 8.3.1snapshot


