On 2015-02-23 09:54-0000 Phil Rosenberg wrote: > Hi Alan > How would you like me to deal with any further wxWidgets bugs this week? > > I would guess that anything contained within the wxWidgets driver > would be okay, however a number of those bugs are plbuffer related. > For example I have just fixed the rotation problem with example 3. I > turned out that the rotation was not saved to the buffer, so this > requires a new command type and new functions in blbuf.c, so it is not > what I would call a trivial change.
Hi Phil: Tough question. Ultimately, it is your call because you are the one who is most familiar with the implications of your decision to push now or wait until post release. However, I will try to answer you as best I can to give you some guide lines about your decision. I think you have it right that any change confined to wxwidgets is probably fine. After all, we do want to improve the new wxwidgets as much as possible before release. And if we fail to do that (say we never do finalize the decision that has been plaguing us about the best way to randomize the names so that showstopping bug (on some platforms like Debian stable) is still there on the day of the release), then you should be mentally prepared for me to disable wxwidgets by default (in consultation with you if I have good e-mail contact with you on the 28th). But hopefully all showstopping bugs like that one will be gone then so we can keep wxwidgets enabled by default. You are also right to be a bit more careful of plbuf changes since they affect more than wxwidgets. For example, I have been told that resizing xwing exercises plbuf functionality. However, so long as you test that your plbuf changes help wxwidgets and do not hurt other PLplot features (such as xwin resizing), then I would say go ahead. So basically the soft freeze is pretty soft right now, but it should gradually harden through the week, i.e., you should get more conservative about changes as the week progresses. Furthermore, even now you should avoid introducing gratuitous changes (i.e., new features) that don't fix existing functionality. But when wondering about whether some push is acceptable, just remember the whole point of this "freeze" is to reduce the probability that your changes introduce new bugs that invalidate tests made this week. So, for example, we will want to be extremely conservative about introducing changes late in the week after so much of the testing has been completed. Hope that discussion of the various factors that affect the push decision during test week helps clarify things for you. 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 __________________________ ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
