Re: On release numbering

[John Stoffel]

>>>>> "Mark" == Mark Diekhans <markd@ucsc.edu> writes:

> Hi John,

> discussion below

> John Stoffel <john@stoffel.org> writes:
>> So I'm now using VM 8.3.0b as the version number is given in git main
>> branch.  When compiling on emacs 28.x on Debian 12 Bookworm, I'm
>> seeing a bunch of warnings like this:

> gitlab main should have a version number of 8.3.x.

Awesome.   I'd suggest you/we append the latest git tag/commit number
into the version string. then it's *really* clear what's happening.  

> I would suggest doing a pull and then rerunning autoconf.  The
> version is in configure.ac

Being able to automagically append to the AC_INIT version something
like:

    git describe --abbrev=7 --dirty --always --tags


Maybe this in configure.ac would work?

  AC_INIT([Title], m4_esyscmd([git describe --abbrev=7 --dirty --always --tags 
| tr -d '\n']))

I'll see if I can make it work.  

>> vm.el:769:1: Warning: ‘defun*’ is an obsolete alias (as of 27.1); use
>> ‘cl-defun’ instead.

> A fix to the defun* issue has been merge.  However, there are
> other warning that need to be fix.  I think most of the easy.

Thanks, I just pulled and I'll re-conpile and see how it looks now.

>> so I'll try to work up a patch, but then I need to test it back to
>> older versions of emacs.  Do we have an idea of how far back we want
>> to go with emacs support?  

> Good question.   My opinion would be ensuring it works with emacs 27
> would be good, but we really have no data to go off of.  It might
> be a wait and see what happens when people use it.

I suspect we should just got with debian 11 as our base, along with
Ubuntu 20.04 LTS, if it's still accepting updates. If not... let's
push to whatever the lowest emacs version is currently shipped on
current stuff.  

Unless someone else has a better idea?

> In the unlikely event that something be warning in an early version,
> but not in 29, I wouldn't worry about it.

Thanks for all your help!
John