Skip to content

1.0b1 release

Dan Villiom Podlaski Christiansen requested to merge topic/1.0.x/1.0b1-release into branch/1.0.x

The upcoming release will be called 1.0 rather than 0.11.0. The main motivation for this is that I consider hg-git “ready”. In order for semantic versioning to make sense, something has to eventually be good enough. With the changes to user experience, I personally consider this good enough to actually use. And besides, if this isn't 1.0, when should it be? When development ceases?

I propose the following versioning policy:

Going forward, major releases, that is x.0.0, will be for significant changes to user experience, especially new features or changes likely to affect workflow. Minor releases, x.y.0, is for less significant changes or adjustments to user experience, including bug fixes, but they needn't retain exact compatibility. Patch releases, x.y.z, will exclusively be breaking bugs and compatibility.

We can drop compatibility for unsupported versions of Python, Mercurial or Dulwich in anything but patch releases.

Cc'ing other maintainers: @gracinet, @krbullock & @mjacob.

Merge request reports