Our last release was way back in February of this year so I think it
would be a good idea to get out another release fairly soon, say 6
weeks from now near the beginning of December.  That is about the
latest time in a year I would like to make a release so as not to
conflict with Christmas holiday plans for anybody here.

Would that sort of time frame for the release be acceptable to everyone?

Currently, I have one more item on my PLplot ToDo list which is to
update all necessary scripts I use in the release process (e.g.,
scripts/make_tarball.sh used to create the release tarball) to replace
svn commands by their git counterparts.  But I am going to wait until
the actual release process to deal with those issues.  Also, assuming
Phil decides to work during this release cycle on an idea he told me
about off list to finally make -dev wxwidgets much more reliable, I
plan to help him with the build-system changes required by his idea.

I also plan to help with propagation efforts.  Here is the current
status of those:

c++
   Missing examples            :
   Differing postscript output :  08
   Missing stdout              :
   Differing stdout            : 
f95
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
java
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
octave
   Missing examples            :
   Differing postscript output :  07 08 19
   Missing stdout              :
   Differing stdout            : 
python
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
tcl
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
ada
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
adathick
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
ocaml
   Missing examples            :
   Differing postscript output :  08 16 19 33
   Missing stdout              :
   Differing stdout            : 
lua
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            : 
d
   Missing examples            :
   Differing postscript output :  08 19
   Missing stdout              :
   Differing stdout            :

It would be good to get all of these issues cleaned up for the release
so I hope everyone helps out with these propagation issues for the
languages where they have expertise.

The vast majority of these issues are due to changes made in example 8
and 19.

The example 8 change is

"Add a 4th (and 8th) page that demonstrates plsurf3dl results for
Y index ranges that follow an ellipse (subject to integer
quantization)."

So to propagate this change for a given language you need to add the
plsurf3dl API to the language binding (if it hasn't been implemented
already) and then modify example 8 for the language.

The example 19 differences are due to Phil's recent addition of the
new functions plmapline, plmapstring, plmaptex, and plmapfill
functions to our API, and adding calls to those functions in example
19 to implement a really nice looking Exmoor map page.  So to
propagate this change for a given language you need to add those new
functions to the language binding, and modify example 19 for the
language.

For this release, I also hope Arjen and Phil adjust the build system
(either by fixing non-working tests for simple issues or removing
non-working tests from the list of what is tested for tougher issues)
so that scripts/comprehensive_test.sh runs without errors for the
various Windows platforms accessible to them (Cygwin, MSYS, MSVC).
This is important because it finally establishes comprehensive test
benchmarks for those platforms that we can use as a basis of future
tests for regressions in our support of various Windows platforms.
Also as I have already mentioned off-list to them, it is easy to
implement a CMake warning message for each test that is skipped to
motivate fixing the non-working tests they discover. Note, this script
already works for the one Windows platform I have access to
(MinGW/MSYS/Wine) so script success on the platforms accessible to
them should require few if any changes.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to