Re: Proposed addition to RC policy (release upgrades)
* Adam D. Barratt (adam@adam-barratt.org.uk) [130917 20:45]:
> As I've seen it come up a few times recently, I'm proposing adding some
> explicit RC requirements relating to upgrades between releases. I don't
> think there's anything particularly controversial about this, as it's
> basically documenting long-standing practice.
yes, this is the current policy.
> | + Packages must upgrade cleanly from the version in the previous stable
> | + release (if any). In order to support partial upgrades, versioned
> | + dependencies must be used if the version in the previous release is
> | + not sufficient for the new package version to be functional. Upgrades
> | + skipping a stable release are not required to be supported.
> | +
> | If two packages cannot be installed together, one must list the other
> | in its "Conflicts:" field.
> \==========================================================
should we also put a statement in about (versioned) conflicts, or does
that follow automatically from the normal text below?
Andi
Reply to: