Re: release plane for 4.0 -- Re: GP_ISVAR, GP_FIT_ERRVARS

[Hans-Bernhard B. <br...@ph...>]

On Thu, 19 Feb 2004, Petr Mikulik wrote:

> Why should we wait till April? 

The April timeline was essentially my invention.

It's to give "4.0 release candidate 0" (that is, 3.8k) some time to
settle: let people out there actually download it after we announce that
it's time for last-minute checking before 4.0 release, run their own
tests, and report whatever showstoppers they might find.  If we don't
allow at least a couple of weeks between 3.8k.0 release and 4.0, there's
no point doing a 3.8k in the first place.  Assuming we can fix all issues
they find in a matter of days would be unprudent.

We also have to organize and carry out binary package builds for all the
important platforms.  For the 16-bit DOS/Windows and part of the Win32
world, that usually means _I_ will be doing it, and I'm not in a position
to rush things like that, right now.

> Do you think that anybody will take care about looking to the frozen
> code of gnuplot for months?

We're talking about roughly 6 weeks, here, or 1.5 months.  That's not
exactly very much.  The code freeze is for *us* to worry about.  It's
about concentrating entirely on bug fixes, while setting aside work on new
features for the time being.
 
> As I've noticed, there were no (serious) bug reports for some months.

But you don't seem to take into account that the vast majority of users
out there are likely not using the 3.8 series to begin with --- all the
major Linux distros have 3.7.3 or older.  The point of a 3.8k release and
a couple of weeks' wating is to get as many of the dormant bugs out into
the light before the actual release version as possible.  What with the
"ask Thomas Williams about it" business and all, an official release cycle
of gnuplot is difficult enough that we don't need the additional
complexity of a 4.0.1 fix-up release four weeks later.
 
> I've noticed people (including some developers!) get very frustrated that
> gnuplot gets releases in timescale of several years. That really makes
> people disappointed. Let's don't do that.

Let me turn that around by looking at the facts.  3.7.3 is 14 months old
right now.  That's neither so long ago that we absolutely have to release
something new very soon now, nor is it so short that delaying for another
month or even two would seem excessive in comparison.  

We are in no hurry unless we impose one on ourselves.

> I propose to release 4.0 on February 27. Or even better on Sunday
> February 29, which better follows gnuplot's release timescales :-))

No, that's definitely too early.

> And release gnuplot-3.8k today.

Let's leave that to Lars, shall we?

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.