[Rubygems-developers] Versioning policy input
chad at chadfowler.com
Mon Apr 5 23:30:21 EDT 2004
On 5/4/2004, at 10:50 AM, Mauricio Fernández wrote:
> On Mon, Apr 05, 2004 at 06:31:48AM -0700, David A. Black wrote:
>>> Add a separate field "APIVersion" with a version number to the
>>> GEM spec,
>>> which specifies API revisioning, and is rigidly formed for that
>> I like the idea of having something in the gemspec that flags API
>> changes. It takes the burden off the public release numbering, so
>> that we wouldn't have to take on the literally impossible task of
>> trying to get all authors to agree on how to (publically) number their
> Please take a look at the attached patches, which contain a
> straightforward implementation of the proposed internal versioning
> B (i.e. the complete, x.y.z one).
Do you prefer B over A for some specific reason? I'm not sure I like
either yet, but if it were up to me right now and I had to pick one of
them, it would be A.
> Note that merging this would cause all existent gemspecs to stop
> working (1)
> since they will be missing the 'api_version' field. I've done some
> ad-hoc corrections to gemspecs/*.gemspec *but* api_version should be
> set by somebody knowledgeable w/ the API for each lib.
I'm not too worried about breaking existing gems. We're in Alpha, and
it's easy to script a fix.
More information about the Rubygems-developers