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

[Petr M. <mi...@ph...>]

> 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.
>
> important platforms.  For the 16-bit DOS/Windows and part of the Win32
>
> 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.

Ok, thus gnuplot-3.8k is released now, including:
- source code tarball
- binary releases for MSW 32bit, OS/2, (and some 16bit?), will full docs
- maybe some RPM package?

We want that
- bugs are reported
- missing Windows et al terminal entries to be added, if contributed

New web page can be put on as well, saying about 3.8k as prerelease.

Announcement should go to all principal application groups -- Octave mailing
list, maybe slashdot and similar? (in CZ, e.g. www.root.cz)

Deadline for 4.0 should be specified. I would like March 31 (5 weeks) ..
somehow I fear April is quite late. (It would be great if new gnuplot goes
into some important Linux distro, like SuSE 9.1. -- if not, it's about
loosing half year then!)


> > 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

As I know, that majority refuses to use software not officially released.
So they won't care about 3.8k anyway.


> 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 see. Does he (and other people) have to agree with 4.0 and with any of its
further releases?

---
pm