On Fri, Jul 31, 2015 at 11:57:59PM +0200, Peter Stuge wrote: > William Hubbs wrote: > > > > [1] http://www.semver.org > > > > > > Major version zero (0.y.z) is for initial development. Anything may change > > > > The problem is that version 0 hit stable > > Just treat version numbers as the meaningless counters they are. They are not meaningless counters if you give them a meaning; that's what semantic versioning is about.
> > I can't just randomly break things from 0.17 to 0.18 for example. > > Of course you can. > > > Wait, actually, nothing should ever break randomly. Compatibility and > so on.. That again is why there is semantic versioning. If you follow the rules there, incrementing the major version number means you changed something in an incompatible way, so people know about it when they get the new release. What I'm asking about is whether anyone knows of a smoothe way to transition users from local/netmount to mount.<filesystem> dependencies, without breaking systems. If that doesn't exist, 1.0 will have to sit in p.mask until major packages catch up. William
signature.asc
Description: Digital signature
