Package: routine-update Version: 0.1.5 Severity: wishlist
I think targeting experimental for breaking changes is a safer default than picking unstable by default.
As per semver.org, for libraries without a public API, ie, version < 1.0, even minor updates can be breaking - even if it does not actually break, most reverse dependencies declare a stricter dependency. Patch updates are usually allowed when declaring dependency relations.
For example in ruby/Gemfile, we usually have ~> 2.0 (stable public API) vs ~> 0.9.0 (no stable API).At least for library packages (this can packages starting with lib, ruby-, python*- etc) we should do this by default.
For other packages also this might still be a safer choice.
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
