My apologies if some of you receive this twice, but my first attempt to post this did not appear in the Plplot-devel list archives and also did not appear to be sent back to me from the SF mail server in a timely manner.
____________________________________________________________________________ To help improve the quality of this forthcoming release I would like to encourage widespread use of our new testing framework AND reporting results of that testing from now until when the actual release occurs (mid-May at the earliest according to Hazen's recent announcement). Accordingly, I have implemented a new table at http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot to help you report your test results, reassure users about what platforms/configurations have been tested, and also to give you public credit for your testing efforts. The Wiki syntax for tables is extremely straightforward. Furthermore, I have already supplied one test report there so once you are logged in (every interested PLplot user is encouraged to get a wiki account, not just core PLplot developers) you can edit the table and cut and paste the wiki table syntax (with no necessity of understanding that syntax in any deep detail) to act as a template for your own report. I have tried to minimize details to make this test reporting as easy to do as possible. Generally you have to identify your platform (including CMake, Pango/Cairo, and Qt versions as well as the general PLplot shared library and dynamic devices fundamental configuration); the actual build and run-time tests that you ran for the build tree and/or installed examples tree; and then add any additional notes you desire about the configuration or test results. N.B. I have recently made a change (revision 10954) so you no longer get the confusing test_noninteractive error result because of differing PostScript or stdout results from equivalent examples. Those differences are important and we should reduce them as much as possible (see previous post today), but this change reserves the error result for serious run-time errors (segfaults, etc.) turned up by test_noninteractive. Of course running and reporting tests is only the first step to a high-quality release. If your build and run-time testing discovers a bug, please report that bug here first in case we can come up with an immediate fix. However, if an immediate fix is not possible, then please report the bug on the bug tracker. For non core developers here, patches to fix open bugs on the bug tracker are most welcome! For the core developers here, please pay attention to fixing any open bugs that have been assigned to you on the bug tracker. Of course, we are all volunteers here with other calls on our time. So if you find you cannot fix a bug in a timely manner that has been assigned to you, please try to hand off the problem to somebody else. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
