gnuplot-beta

Timeframe for 4.1 release?

[Per P. <per...@ma...>]

Hi,
is there a estimated ETA for gnuplot 4.1?
I'm working on enhanced text support for aquaterm and I'd like to have 
it well tested by then...

/Per

Re: Timeframe for 4.1 release?

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

Per Persson wrote:

> is there a estimated ETA for gnuplot 4.1?

No.  gnuplot has esentially never used time as a planning instrument 
outside those phases when releases were actively being put together.

In other words, the ETA is "whenever we think it's ready".

Re: Timeframe for 4.1 release?

[Ethan M. <merritt@u.washington.edu>]

On Wednesday 13 October 2004 03:53 am, Per Persson wrote:
> Hi,
> is there a estimated ETA for gnuplot 4.1?

Heh.  Not likely.

But I do think it is worth putting out a 4.0.2 bugfix release.

It's been 6  months, and we've gotten several real-world  
bug reports for things that had already been fixed in the 
branch-4-0-stable cvs tree.

-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

Re: Timeframe for 4.1 release?

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

> But I do think it is worth putting out a 4.0.2 bugfix release.
>
> It's been 6  months, and we've gotten several real-world
> bug reports for things that had already been fixed in the
> branch-4-0-stable cvs tree.

I think so too.

Is there the fix for the "white line" bug in the combination of postscript +
pm3d + gs8.x + antialiasing? That would be worth it.

--
PM

Re: Timeframe for 4.1 release?

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

Petr Mikulik wrote:

> Is there the fix for the "white line" bug in the combination of
> postscript + pm3d + gs8.x + antialiasing? That would be worth it.

Since we only know how to trigger it, but never quite found out *why* it
happens, I don't see any way of fixing that one.  Maybe someone should
file a ghostscript bug for that one?