From: Joao C. <jc...@fe...> - 2002-01-18 14:27:47
|
On Friday 18 January 2002 2:54 am, Alan W. Irwin wrote: > On Fri, 18 Jan 2002, [iso-8859-1] Jo=E3o Cardoso wrote: > > On Thursday 17 January 2002 17:15, Alan W. Irwin wrote: =2E.. > > [....] My not yet commited plimage() changes and related > > functions are yet alpha. At this point I'm afraid of commiting my > > changes, as perhaps the current cvs plimage() is more stable than > > mine. > > But the point is this does not affect anything other than x20c. It wou= ld > be a much tougher decision if you were fiddling with the very inner cor= e of > plplot, but you are not. I'm not sure about that. Working with plstrm.h, plcore.c, plbuf.c and xwi= n.c=20 might break others things. > I hope to get out the next release within a month > or two so if you make a mistake with plimage now, it will soon get > corrected. So I am inclined to say that if x20c still works on your > platform with all your uncommitted changes, then go ahead and commit th= em. > However, if you are not comfortable with that, that is fine as well. > Ultimately, of course, it is your decision. I have checked out a clean cvs and test x20c; it's more stable than my=20 current cvs, so I will not commit my changes for now. =2E.. > > What I mean is that 5.1 is too definitive for the current status. > > As you say, we are not many, and can't afford the pressure of a > > faulty major release. > > My understanding of release traditions is quite different. Patch versi= on 0 > of anything is never expected to be reliable. Compare kernel 2.4.0 wit= h > 2.4.17 or KDE 2.2.0 with 2.2.2, for example. But it is not "intencional". We *know* that, given the nature of things,=20 version 0 is unstable, no matter the efforts developpers made. But if you= =20 look at KDE, e.g., the 0 release is quite usable and is followed shortly = by a=20 bug correcting release. Gnome has even a shorter history release. But as Geoffrey said, you are the boss in this matter, and I'm glad you a= re=20 :-) Joao |