[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] Re: rfc: openrc mount service prototype
From:       Duncan <1i5t5.duncan () cox ! net>
Date:       2015-07-31 23:18:15
Message-ID: pan$65f4f$edad90cf$d57c69c9$9e55e89f () cox ! net
[Download RAW message or body]

William Hubbs posted on Fri, 31 Jul 2015 16:43:48 -0500 as excerpted:

> On Fri, Jul 31, 2015 at 10:27:02PM +0200, eroen wrote:
>> On Fri, Jul 31, 2015 at 02:49:08PM -0500, William Hubbs wrote:
>> > I'm still looking for ideas of ways to avoid making this a breaking
>> > change. If it isn't possible to make it a non-breaking change, this
>> > will force openrc-1.0 to be the first release where we can do this
>> > (going from 0.x to 1.x signifies breaking changes in semantic
>> > versioning [1]).
>> 
>> > [1] http://www.semver.org
>> 
>> This is a valid and possible versioning policy, but it is not semver.
>> Your [1] states:
>> 
>> 4.  Major version zero (0.y.z) is for initial development. Anything may
>>     change at any time. The public API should not be considered stable.
> 
> The problem is that version 0 hit stable before I knew about semver, so
> I have to treat version 0 as version 1.
> 
> I can't just randomly break things from 0.17 to 0.18 for example.

I've seen others in that predicament do a much larger jump, say to 0.80+ 
or adding a digit.  The atypically large jump seems to signify a broken 
API well enough.

So what about jumping from 0.17 to 0.100, or possibly to 0.80 or 0.90, if 
you intend to jump to 1.0 reasonably soon, since x.8y and x.9y are 
reasonably often used for betas and rcs, respectively.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


[prev in list] [next in list] [prev in thread] [next in thread]