The 5.9.11 release process is finished. (Ironically, that coincided almost perfectly with when the University of Victoria finally fixed my incoming mail issues!)
The svn commit freeze that was in effect is now thawed, and I look forward to your commits for our next release (5.10.0) of PLplot which will be our first stable release since 5.8.0 was released 6 (!) years ago. My initial plan (always subject to change depending on your needs) is to make this release cycle short (a month or so) and mostly devoted to fixing bugs. I hope, for example, we can clear up most of the bugs that we discovered in the closing stages of the 5.9.11 release cycle, but which we did not have time to fix before the 5.9.11 release. (Just search our mailing list over the last two weeks for the phrases "post" and "release" which occurred together in quite a few discussions.) Tcl/Tk/Itcl/Itk/Iwidgets issues are a special case for this release cycle. Most of the burden of fixing those will fall on Arjen because he is the only active PLplot developer with expertise in those languages, and I do not want to restrict what he does to just bug fixing. Instead, I strongly encourage him to deliver more than just bug fixes during this release cycle. In my opinion it has been too long since our Tcl, etc., bindings and examples got a lot of attention from an expert. There are bound to be some fairly large things he wants to change, and I believe such changes are okay for a "stable" release so long as we thoroughly test Arjen's changes on the platforms accessible to us, and our release notes clearly state the relatively large changes that have gone on. During this release cycle I plan to work almost exclusively on epa_build which will also be a special case with more than just bug fixing in this stable release cycle. I think this is OK since epa_build is so immature in any case. Are there any other special (more than just bug-fixing) development cases out there for this stable release cycle? If so, please let us know about them now if you think they are appropriate. But if you think your PLplot development is not suitable for a stable release cycle, I would still encourage you not to wait, but instead develop now on a branch that can be merged in later during our next series of development releases. Best wishes for the Christmas season and our shiny new release cycle! 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 __________________________ ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
