Re: Release 5.2.1

[Ethan A M. <sf...@us...>]

On Monday, October 30, 2017 12:30:22 PM PDT Daniel J Sebald wrote:
> On 10/28/2017 02:17 PM, sfeam via gnuplot-beta wrote:
> > It is not clear when the cvs->git conversion process will settle down
> > to
> > the point where I am comfortable preparing an incremental release
> > from the new git repository.  Rather than waiting for that, I would
> > rather package up 5.2.1 from a final cvs snapshot plus a couple of
> > last-minute fixes that I will maintain on the side until the git
> > conversion completes.

> Updating CVS is fine, as the ./reconvert script gathers the latest
> version of the code.  

I wish someone had made that clear earlier.  
I asked about a freeze and thought that the response was "yes,
a freeze would be good".   OK, I'll go ahead and commit the 10-12
changesets that I applied locally to prepare the 5.2.1 tarball.

Maybe then it should be repackaged as 5.2.2?   There has been 
at least one request for a fix-to-the-fix since I packaged up 5.2.1. 

> Don't want to make the first thing you do under git be a release.

Exactly.  Also I worry that we may turn up additional glitches in the
conversion once serious develoment resumes.

	Ethan

> 
> Dan