I have been making steady progress of my list of things I want to get
done before PLplot-5.12.0 is released.  Currently I am working on a
big update to the DocBook documentation, and after that is completed
and uploaded to the website, I plan to call for widespread testing of
the new Fortran binding based on that updated documentation. However,
there is still quite a few more topics on my list other than those two
items so I plan to hold off declaring the freeze on merges of major
topics to master until one month from now.

So this continues to be a good opportunity for the rest of you to
merge in your own matured development topics to master. Here is a list
of such topics that I am aware of where I believe there is still a
chance for you to mature them during this release cycle rather than
waiting until after the release of 5.12.0.

Arjen: Tcl and Fortran fixes.

Phil: wxwidgets bug fixes (especially concerning the severe
inefficiency issue on Linux that I documented). Implementation of
uniform reporting of memory allocation errors using exit (as a
preliminary to the planned post-release implemention of a proper error
report system).  Once Phil has designed plmalloc, plcalloc, and
plrealloc, I would be willing to help with the editing work of
replacing all our current raw calls to malloc, calloc, and realloc
with those PLplot equivalents which treat errors in a uniform way
(currently with exit, but that should be convenient to update later
once the proper error report system has been implemented).

Jim: plmeta, plbuf, and wingcc fixes and implementation of his enhanced
wingcc device.

Jerry: fix Ada issues (the current PostScript differences for examples
8 and 19).

Both Jim and Jerry have told me off-list that merging a git topic
branch to master is still somewhat intimidating for them. To bypass
that issue for now I suggest you both proceed by simply sending
patches to this list.  Patches formatted by "git format-patch" would
be ideal (since that approach gives you automatic git credit for your
work in a standard way), but ordinary patches are still acceptable as
well if you are having trouble getting good results with the "git
format-patch" command.

Here is my proposed schedule for PLplot development leading up to the
5.12.0 release:

* In the next few days: Call for widespread testing of the new Fortran binding.

* In the next month: Lots of merges of matured work from all of us to the
master branch.

* 2016-04-09: Freeze for all but simple bug fixes and documentation
updates.

* In the month after the freeze date: Comprehensive testing on as many 
platforms as are accessible to us.

* 2016-05-07: Release of PLplot-5.12.0.

Please let me know if anyone has issues with this proposed schedule of
events leading up to the release of PLplot-5.12.0.

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
__________________________

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to