Just read the document at http://semver.org/ fully and this sounds like a sensible approach. Since I think with crate metadata it should be obvious (at the symbol level) if the public api changes, then this can be tracked somewhere by an automatic tool where we have a public list of rust packages (rustpi or travis etc).
On Sat, Feb 1, 2014 at 6:59 PM, Lee Braiden <[email protected]> wrote: > On 01/02/14 18:54, Gaetan wrote: > >> why not enforcing in a way or another a API compatibility test suite for >> ensuring at least a certain level of compatibility between two version? I >> think it is something quite doable, and moreover this would kinda force the >> package manager to write unit tests which is always a good practice. >> > > At the moment, we're trying to agree the policy. After the policy is > agreed, tools could be created to help ensure that those policies are met. > People would then use them if they see fit, or they could be built into > package creation / version upload tools as standard. The first thing is to > agree a reliable, sensible policy that improves the quality of software / > package management, and is WORTH enforcing, though. > > > -- > Lee > > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
