Original version numbering was simply incremental (e.g. v3.0.7 is newer than v3.0.4). Since 2016, the version numbers represent year and month. E.g. v16.12 is from December 2016.
On Sat, Apr 22, 2017 at 7:17 PM, Christopher Howard < christopher.how...@qlfiles.net> wrote: > What is the significance of the version number components (major, > minor...)? Does versions 17.6 and greater aim for backwards > compatibility with 16.12? > > On 04/21/2017 09:03 AM, Mansur Mamkin wrote: > > Hi all! > > > > I've extended my previous script that handled > > https://bitbucket.org/mmamkin/picolisp/ > > > > Now we have also git-repository at https://github.com/picolisp/picolisp > > > > https://software-lab.de/picoLisp.tgz is checked four times a day and new > > commits are created when it has changed > > > > Best regards, > > > > Mansur Mamkin > > > > > > > > > > -- > https://qlfiles.net > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > -- *-- Frantisek Fuka* (yes, that IS my real name) -- My Personal homepage: www.fuxoft.cz -- My Google+ profile: google.com/+fuxoft -- My Telegram chat: telegram.fuxoft.cz
