Go to file
Wolfgang Bumiller 1a2aaad5a1 more versioning fixups
Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-30 12:33:13 +01:00
proxmox -dev bump for proxmox crate as well 2019-12-30 12:05:57 +01:00
proxmox-api more versioning fixups 2019-12-30 12:33:13 +01:00
proxmox-api-macro proxmox-api-macro: initial packaging 2019-12-20 09:39:45 +01:00
proxmox-sortable-macro proxmox-sortable-macro: initial packaging 2019-12-20 09:39:45 +01:00
proxmox-sys more versioning fixups 2019-12-30 12:33:13 +01:00
proxmox-tools bump proxmox-tools to 0.1.1-dev.1 2019-12-30 11:32:21 +01:00
.gitignore import Cargo.lock 2019-08-09 08:44:48 +02:00
Cargo.toml delete the old api macro stuff 2019-11-21 13:13:18 +01:00
Makefile run 'cargo fmt -- --check' in check target 2019-11-25 15:08:53 +01:00
README.rst more versioning fixups 2019-12-30 12:33:13 +01:00
rust-toolchain update toolchain to stable 2019-11-08 11:51:21 +01:00
rustfmt.toml initial import, starting with vec & io helpers 2019-06-06 14:00:25 +02:00

Versioning
==========

Note that the following applies *per crate*, since each crate is its own debian package:

The first commit after a release should bump the version to the next patch level with a ``-dev.1``
suffix for the crate *and for the proxmox crate*, as well as all crates depending on it. For
instance, ``proxmox-api`` depends on ``proxmox-tools``, so bumpgin ``proxmox-tools`` to a new `dev`
version also requires bumping ``proxmox-api`` to a new dev version, since cargo requires
pre-release versions to be selected explicitly:

    First commit after release: 0.1.0 -> 0.1.1-dev.1
    Version bump commit: 0.1.1-dev.1 -> 0.1.1

It is unlikely that we'll need more than one .dev version, but it may be useful at some point, so
we'll include teh ``.1``.

When releasing a crate, the final commit should be the one stripping the ``-dev`` version and
updating the ``debian/changelog``.