> SemVer explicitly do not support stability across major releases, which > implies that no stability is promised about a feature having same API across > major releases.
Are you talking about the availability/unavailability of certain features? If yes, all of debcargo-conf's packages involved in the 2->3 transition depend on the default feature, so it would be enough to Provide librust-lazy-regex+default-dev. If not I'd appreciate it if you could elaborate on > Individual packages are still free to not care about SemVer but then need to > fully admit that by depending on the core crate, without features. It may be my inexperience talking, but it is unclear to me how features are involved here. How does "depending on the core crate, without features" equate to fully admitting that a package does not care about SemVer (if not for the availability/unavailability of features)? I don't understand what features add to this, logically.
