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

On Fri, Jan 09, 2004 at 02:59:27PM -0600, kfogel@collab.net wrote:
>...
> I do think we have a real problem here. We can't change APIs without
> calling it 2.0, yet we've reason to believe we'll want to fix up some
> APIs *before* we have enough new features to justify calling it 2.0.

You can add functions until the cows come home. You just can't change an
existing function. That's a big difference, and leaves a LOT of room for
growth and overall change.

> I'll mull on this a bit and see if I can come up with a [good]
> proposal to deal with the problem. I had also tossed out another
> possibility, saying "Another solution is to just have four numbers?"
> But haven't really thought that one through carefully.

We'd have releases like:

  1.1.0.0
  1.1.1.3
  1.1.4.1
  1.2.0.3
  1.2.1.1
  2.3.0.4
  2.3.1.0

Note that the second part is monotonically increasing, as that would be
the major API version.

Dunno about it altogether tho... I certainly haven't thought on it :-)

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