Versioning and development issues

[Jan Wielemaker-3]

Hi,

I'm getting closer to releasing 5.8.0. Because more and more things are
going on with and around SWI-Prolog, the release and versioning
processes are becomming more important. This is particularly true for
developers. Below is the plan, which is being executed. GIT is pretty
flexible though, so if you think it can be done better (or with less
administrative work), please let me know.

    * pl.git is the stable version,  That has always been the idea,
      so I merged pl-57x.git on top of pl.git and start calling it
      5.8.X (done).

      This is the basis for the stable binaries (to be created shortly)

    * Development was on pl-57x.git.  This is a bit unfortunate, as
      we now want to start 5.9.X, but we don't want all developers
      to rename their git setup.  So,

        * I renamed it into pl-devel.git
        * I created a link pl-57x.git --> pl-devel.git, so you
          can continue for now as you did.  Please update
          your git setup to link to the new git (edit .git/config).

    * The master branch of pl-devel.git is supposed to be mostly in a
      useable state.  As always, shit happens, but we do not place stuff
      there which we knows to smell so badly that it is likely to frustrate
      other developers for a long time.  This was more or less the
      current practice on pl-57x.

    * Dangerous and experimental stuff goes on its own branch, until the
      developer thinks it is ready for intended users of the master
      branch.

SWI-Prolog 5.9.X
================

The aim of 5.9.X is to enhance memory management.  In particular:

    * Replace allocation of the stacks using sparse management of
      the address-space with relocating the stacks.  The new implementation
      allows for SHIFT/GC almost anywhere, and can thus live with small
      margins between allocated address-space and in-use stack-area.
      (it defines a programmable `spare' stack size that is enabled
      for processing exceptions, such that it can process (stack-)
      resource exceptions).

      Finished, but likely to be still buggy.

      This work is on the branch `shift'

    * Remove max_threads (limited only by OS/resources)

    * Enhance segment-handling, reducing trail requirements (partly
      implemented).

    * Implement incremental GC (what is the proper name): GC'ing only
      the part after the previous GC.

At the moment, I to make that the stable version as soon as it proves as
stable as 5.8.0.

        Enjoy --- Jan

_______________________________________________
SWI-Prolog mailing list
SWI-Prolog@...
https://mailbox.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog