Status update - version 5.2.2, cvs->git conversion, plans

[sfeam <sf...@us...>]

Version 5.2.2
=============

A tarball for release 5.2.2 is now in the usual place on sf.net:
     https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.2/
This will be the last gnuplot release prepared from the CVS repository.

Anything you commit to cvs between now and whenever sourceforge pulls
the plug on it will not make it into future gnuplot releases.

cvs->git conversion
===================

A snapshot of the cvs repository from 04-November-2017 was converted
to git with the help of Eric S Raymond [Thanks!]
Since then we have been evaluating the state of the converted source tree.
At the moment there are two copies on sf.net, one slightly cleaner than
the other.  A handful of commits have gone in to these, but it remains
true that the existing git content on sf.net may be wiped clean and
re-created from the 04-Nov-2017 snapshot if we find that there were
annoying but correctable errors from the previous conversion[s].
So far the "correctable" part has been a sticking point.

plans
=====

I will be travelling for most of the next month, so I would prefer that
we make a yes/no decision by next Monday (20 November) as to whether the
current converted code base is good enough to work with.  If it is not,
then the repository is likely to remain volatile until at least the end
of the year.  You'll be able to read from it, but if you make copies
you may have to rebase or re-clone if we do the entire conversion over
again.

But really I think it all looks promising. 
Not perfect but "good enough".

Questions
=========

I'm still learning how to rethink my work flow for git, so please
help me out.   For instance, does it make any sense to continue
to maintain the ChangeLog file?   So far I'm having little success in
keeping it in sync with the git commit messages.  Is there some
tool to help with that, or is the normal practice with git to rely
only on the commit messages?  I know you can dump a log of commits,
so I guess one possibility is to use that to update the ChangeLog every
now and then (1 month intervals? 6 months?) but not try to touch it
for every commit.  Advice?

	Ethan