Date: Mon, 10 May 1999 13:48:48 +0930 (CST) From: Kris Kennaway <kkennawa@physics.adelaide.edu.au> To: Eivind Eklund <eivind@FreeBSD.org> Cc: "Kenneth D. Merry" <ken@plutotech.com>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/camcontrol camcontrol.8 camcontrol.c src/sys/cam cam_ccb.h cam_sim.c cam_sim.h cam_xpt.c src/sys/cam/sc Message-ID: <Pine.OSF.4.10.9905101343320.14351-100000@bragg> In-Reply-To: <19990510054516.V76212@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 May 1999, Eivind Eklund wrote: > I will repeat myself: Breaking binary compatibility in -stable is > *supposed to be an event*. This means that if you are doing it, you'd > better be doing it for a reason that is good enough to send a message > to -announce. I have to agree with this. Suppose a third-party vendor was producing CAM-using code in binary form: this is no longer usable when people upgrade. This can only hurt us. -STABLE is supposed to be the branch which people can follow without having to worry excessively about whether or not it will break things for them..we /want/ users to track close to the head of the branch (at least the most recent release), and this is much less attractive if it involves people auditing their systems for things which will be broken by the upgrade (of course, people still need to have their eyes open when they do it, but it shouldn't be a major event). Kris ----- "That suit's sharper than a page of Oscar Wilde witticisms that's been rolled up into a point, sprinkled with lemon juice and jabbed into someone's eye" "Wow, that's sharp!" - Ace Rimmer and the Cat, _Red Dwarf_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.4.10.9905101343320.14351-100000>