Sync version numbers of 5ever crates?

[nicoburns]

How would people feel about updating the version numbers of html5ever, xml5ever and markup5ever to be the same, and then keeping them in sync going forwards?

I think this would be easier both for 5ever maintainers and for consumers of the 5ever crates.

[simonwuelker]

That feels weird, because xml5ever and html5ever can be used independently of each other.

[jdm]

Yeah, I've been thinking about this on and off, and it doesn't feel like a meaningful reduction in work as a consumer of the crate, and it potentially leads to an unnecessary increase in breaking version releases.

[nicoburns]

My take is that upgrading to a new "breaking" version that doesn't actually contain any changes is trivial (/not a big deal), whereas figuring out which markup version matches the version of xml/html you're using is annoying (and matching html to xml too if you're using both). And internally we keep getting the release PRs wrong because we're not updating the versions in all the correct places.

But eh. I don't care strongly about this. Maybe an alternative would be to create a table of compatible versions in the README. And perhaps get rid of the Cargo.toml lines in the crate-specific READMEs (as those are what keep getting out of sync).

[simonwuelker]

whereas figuring out which markup version matches the version of xml/html you're using is annoying

Perhaps html5ever/xml5ever should re-export all necessary pieces of markup5ever, such that you never use markup5ever directly, thus removing the need to find a compatible version?