-
-
Notifications
You must be signed in to change notification settings - Fork 170
Release uefi-macros-0.9.0, uefi-0.18.0, and uefi-services-0.15.0 #557
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
Comments
I agree it's about time for a release, I can take care of that early next week, maybe Tuesday. |
Very nice! I'm already having enough ideas for breaking changes for |
We don't have a well-defined release schedule, we publish new versions whenever we feel like it and get around to doing it 😆 that being said, we do have a well-documented release publishing process. @phip1611 would you like to be added as an owner on the crates.io packages as well, so that you can also publish new versions of the crates? |
@GabrielMajeri if you don't mind, sure. |
Done, you should be able to see some owner invites in your inbox now. |
Thanks! Crates.io sent me 4x the same email, tho 😂 |
Weird, there should've been four different invites for the four crates we have ( |
Ah, now I have all invitations. But some of those were sent multiple times. |
From #534 (comment) I've found that we can also safely bump the MSRV with the next release, as enough time has passed. 🎉 |
Ah, @GabrielMajeri , I just noticed that you invited everyone individually Perhaps, it also might be smart to invite |
Release done :) |
Very nice, thank you! |
Sure, you can go ahead and experiment. I had no idea you could invite GitHub teams to own crates 😅 |
Hey, I'm not sure about our release process and how we plan to release certain versions. But I just noticed that we already have lots of new and changed functionality since 0.17.0 written down in the Changelog. Do we want to publish everything as
0.18.0
before the next release gets way too big (breaking changes etc)?@nicholasbishop @GabrielMajeri
The text was updated successfully, but these errors were encountered: