On 2009-05-04 09:16-0400 Hazen Babcock wrote: > Alan W. Irwin wrote: >> Hi Hazen: >> [...]It appears Mac OS X users of 5.9.3 are going to have to patch their >> systems >> for the entirety of the 5.9.3 release cycle. To reduce that user pain as >> much as possible, I suggest that release cycle should be shortened as much >> as possible. Thus, Hazen, once you are happy with your Mac OS X tests, I >> suggest you do a full 5.9.4 release today (Sunday) or tomorrow remembering >> to repeat all the version-specific stuff in README.Release_Manager_Cookbook >> for 5.9.4. >> >> Meanwhile, every other developer should refrain from commits to give Hazen >> a >> clear field to deal with this simple, but nevertheless embarrassing issue. > > Well I hope someone will step up and fix the example 32 problem I mentioned.
That example is a special one which is still being developed/considered. >From the commit message for examples/c/x32c.c "For now this is built automatically, but not included in the test suite or propagated to other languages. Please leave this way until it has been discussed further on plplot-devel." Therefore, you should ignore this example for at least this bug-fix release or patch. I have just mentioned the possibility of a patch instead of a formal release because I think speed is essential. So if you don't have time to do a formal 5.9.4 release today (with especial care taken to get the version numbers and everything that depends on them like the website updated consistently) we could propagate a macosx patch to 5.9.3 (called, e.g., plplot-5.9.3.macosx.patch which should be largely self-explanatory) instead. If you prefer the patch approach, I would need you to first create a tested aqt.rc.in file and commit it. After that I could do everything else, i.e., generate the patch, propagate it to SF, make the associated announcement, etc. This approach adds a patch file that macosx users have to download and apply so it is probably not as good as a formal 5.9.4 release. However, a formal 5.9.4 release takes more time, and if you are tired or rushed there are some possibilities for screwing up the version numbers in an inconsistent way unless you religiously follow README.Release_Manager_Cookbook. Let me know which approach you want to do. 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 __________________________ ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
