Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove MSRV guarantee #746

Merged
merged 2 commits into from
Dec 30, 2018
Merged

Remove MSRV guarantee #746

merged 2 commits into from
Dec 30, 2018

Conversation

Osspial
Copy link
Contributor

@Osspial Osspial commented Dec 22, 2018

As per discussion in #743. Closes #743.

CHANGELOG.md Outdated
@@ -16,6 +16,7 @@
- On Wayland, DPI calculation is handled by smithay-client-toolkit.
- On X11, `WindowBuilder::with_min_dimensions` and `WindowBuilder::with_max_dimensions` now correctly account for DPI.
- Added support for generating dummy `DeviceId`s and `WindowId`s to better support unit testing.
- **Breaking:** Removed minimum supported Rust version guarantee.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how much of a breaking change this is. I mean, compatibility is already broken in 0.18.0...

On that same note, should we remove the entry from 0.18.0 about the 1.28.0 change? That was something I added after release, so it's always felt a bit weasely, and it's not even true anymore.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we remove the 1.28.0 line from the changelog, I feel like we should remove all MSRV lines from the changelog. I'd be fine with doing that, but I don't feel too strongly either way.

Copy link
Member

@francesca64 francesca64 Dec 24, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any other MSRV lines in the changelog, though? The only other mention of MSRV changes I see is under 0.10.0, and that feels a bit different to me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eh, fair enough. Just to be clear about where we stand: this shouldn't be marked as a breaking change but still be in the changelog, and the 1.28 change should be removed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's my position, yes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM. Those changes have been made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants