Re: API-changing releases was Re: concerns about issue #1682

On Thu, Jan 08, 2004 at 04:48:24PM -0600, kfogel@collab.net wrote:
>...
> It seems to me like we have four concepts conflated in three numbers:
>
> a. Major feature additions
> b. API changes
> c. Changes that break binary compat
> d. Changes that maintain binary compat.
>
> Currently, (a) and (b) live in one number, the major version, and the
> others have their own numbers. My reshuffling gives (a) and (b) each
> their own number, and puts (c) and (d) in one number, the patch
> level.

You have to have a number to discriminate between "break compat" and "not
break", yet your proposal conflates those. Thus, you can never tell.

Frankly, I'd like to request that you put a LOT more thought into the
problem before making any kind of proposal or suggestion. I put a ton of
thought into the rules APR and we are using now, with a lot of great ideas
incorporated from Havoc Pennington's document. It is somewhat annoying to
get drive-by suggestions / proposals that don't appear to have the same
depth of thinking and have some real issues with them.

Stop, think, and then post. I understand that you're possibly seeking to
build a proposal organically with the other developers on this. I'd still
ask for a well-thought proposal first, simply to avoid the long churn on
the list for a topic that (IMO) is pretty well thought thru (with the
caveat that some people want a "feature version" somewhere).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org