Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prepare Stylo for a
v0.2.0
release. Closes #95.Dependencies
Before merging this and releasing we should:
This PR builds on:
Notes
I have gone for a simple versioning scheme where all
stylo*
crates have the same version. This means we don't have to worry about breaking vs. non-breaking changes for subcrates. And it makes it simple for consumers of Stylo to work out which version of the subcrates they ought to be depending on.selectors
andservo_arc
are still separately versioned.I propose that we (permanently) keep the following diff downstream:
version = "x.y.z"
line inCargo.toml
stylo
's dependency onstylo_traits
, but NOTstylo
's dependency oncssparser
).This will allow us to avoid triggering Gecko's/Mozilla's auditing process every time we bump a version number. And we need to maintain some level of diff of for
Cargo.toml
files anyway.Release Process
cssparser
v0.35 (Bump version to v0.35.0 rust-cssparser#404)cssparser
v0.35:to_shmem_derive
andservo_arc
). A release order which should work is:cssparser
bump)(Servo will also need to be updated to
cssparser
v0.35, but that doesn't block this PR or Stylo release)