Dependency freeze and optional dependencies

Ben Cooksley bcooksley at
Tue Mar 20 06:02:11 UTC 2018

On Tue, Mar 20, 2018 at 2:58 PM, Michael Pyne <mpyne at> wrote:
> On Tue, Mar 20, 2018 at 12:43:40AM +0100, Albert Astals Cid wrote:
>> Should we allow new features that require optionally a new version of an
>> existing dependency?
>> e.g. Okular depends on libtsd 0.1 and now i want to add a feature that
>> optionally depends on libtsd 0.2, but if you have libtsd 0.1 it's all fine
>> (i.e. it compiles but you don't get the new feature).
>> Does that count as breaking the dependency freeze?
> I think that should be OK, and not counted as breaking dependency
> freeze.

I agree that this should be considered perfectly acceptable.

As long as it's only new features which won't be available, there
should be no reason why newer versions of current dependencies, or new
optional dependencies should be considered a breakage of the
dependency freeze.

> Regards,
>  - Michael Pyne


More information about the release-team mailing list