On 9/14/20 11:40 AM, Fabio Valentini wrote: > On Mon, Sep 14, 2020 at 8:38 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: >> >> On Mon, Sep 14, 2020 at 2:34 PM Zbigniew Jędrzejewski-Szmek >> <zbyszek@xxxxxxxxx> wrote: >>> >>> On Mon, Sep 14, 2020 at 10:10:30AM -0400, Ben Cotton wrote: >>>> https://fedoraproject.org/wiki/Changes/Rust_Crate_Packages_For_Release_Branches >>>> >>>> == Summary == >>>> >>>> This Change proposal aims to enable shipping Rust crate packages >>>> (<code>rust-$CRATE_NAME</code>) on release branches of fedora. >>>> Currently, they are only available for rawhide, which makes building >>>> Rust packages for release branches difficult. >>> >>> Should the update policy for rust-devel packages be relaxes in stable >>> releases to allow updates to follow rawhide, at least if there are >>> no major breaking changes? >>> >>> Current update policy states that major version changes should be avoided >>> in after stable release. But rust upstreams tend to move quickly, so having >>> ~1 year old packages in stable Fedora might not be too useful to build >>> newest upstreams. It might make sense to allow the rust-*-devel packages >>> to be updated more aggressively. >>> >> >> This is probably a good idea. > > I agree. The only thing to keep in mind for semver-incompatible -devel > package updates is to check dependent packages, and either patch them > to use the new version (like in rawhide), or create compat packages if > necessary - so no broken dependencies are generated in the stable > branches. Are we going to recommend that these devel packages are still not really for end users? Otherwise, checking dependent packages is not sufficient. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
