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