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

Start work on rustix 1.0 #1030

Closed
morr0ne opened this issue Mar 1, 2024 · 3 comments
Closed

Start work on rustix 1.0 #1030

morr0ne opened this issue Mar 1, 2024 · 3 comments

Comments

@morr0ne
Copy link
Contributor

morr0ne commented Mar 1, 2024

Rustix has been on version 0.38.x for a while and work towards a 1.0 release seems to be a bit stale. There is already a 1.0 issue here #753 but it does not seem like any work has actually started. I feel like rustix should begin moving forward and start working on a 1.0 release.

Ideally the following things would happen

  • The current main branch would start accepting breaking changes
  • Create a new 0.38 branch based on the current main to keep supporting that version
  • Start releasing "release candidates" for the 1.0 version on crates.io

The work required for a 1.0 release is quite lengthy has highlighted in #753, this would allow to start working on some of it.

I am aware the a 1.0-staging branch already exists but it currently only houses 2 commits which could be easily pulled into the main branch

Finally it would probably help adding a corresponding project and issue label to better track the changes

@notgull
Copy link
Contributor

notgull commented Aug 23, 2024

+1 to this. I'd like to start working on removing the last appearances of linux-raw-sys in the public API.

@sunfishcode
Copy link
Member

My rough idea right now is to finish up #1118 (or figure out an alternative) and anything else ready to go in that time, and then do a 0.38.35 release. If there's anything I'm missing that would be good to get into 0.38.35, please do ping. Once that's out, create a 0.38 maintenance branch, merge 1.0-staging into main, and main can target the eventual 1.0 release.

@sunfishcode
Copy link
Member

This is now done. main is now accepting semver-incompatible changes, and 0.38 releases are now done on a 0.38 branch.

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

No branches or pull requests

3 participants