33 lines
1.4 KiB
ReStructuredText
33 lines
1.4 KiB
ReStructuredText
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``.
|
|
|
|
Local cargo config
|
|
==================
|
|
|
|
This repository ships with a ``.cargo/config`` that replaces the crates.io
|
|
registry with packaged crates located in ``/usr/share/cargo/registry``.
|
|
|
|
A similar config is also applied building with dh_cargo. Cargo.lock needs to be
|
|
deleted when switching between packaged crates and crates.io, since the
|
|
checksums are not compatible.
|
|
|
|
To reference new dependencies (or updated versions) that are not yet packaged,
|
|
the dependency needs to point directly to a path or git source.
|