Date: Tue, 9 May 1995 18:35:54 -0700 From: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: wollman@halloran-eldar.lcs.mit.edu Cc: paul@isl.cf.ac.uk, bde@zeta.org.au, ache@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-gnu@freefall.cdrom.com Subject: Re: cvs commit: src/gnu/lib/libreadline Makefile Message-ID: <199505100135.SAA16944@forgery.CS.Berkeley.EDU> In-Reply-To: <9505091517.AA09817@halloran-eldar.lcs.mit.edu> (message from Garrett Wollman on Tue, 9 May 1995 11:17:29 -0400)
next in thread | previous in thread | raw e-mail | index | archive | help
* > I thought we agreed that it would get bunped *once* per release. * * Indeed we did so agree. * * (Well, closer to the mark, I recommended establishing such a policy, a * few people stated their agreement, and nobody objected at the time.) Ok...then let me reiterate the proposal. ========<from here>======== The version number gets bumped the first time someone changes something in a library (in a visible way from the caller) after a release. It stays there until the next release (except, of course when the first change requires a minor number change and the second requires a major number change), so people modifying the library should check the commit logs before changing the version numbers. Note: The following events cause major version numbers to be bumped (1) deleting a function (2) interface change (different argument order, etc.) and the following events will require the minor number to be bumped (3) adding a function In general, a x.y library can be substituted for x.z if y > z, and this is the only possible substitution. =========<to here>========= If nobody objects, then this will become the official policy. :) Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505100135.SAA16944>