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.

Sign up for GitHub

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

Jump to bottom

Re-organize changelog to make updating to 0.6 easier #1247

Closed
davidpdrsn opened this issue Aug 11, 2022 · 2 comments · Fixed by #1274
Closed

Re-organize changelog to make updating to 0.6 easier #1247

davidpdrsn opened this issue Aug 11, 2022 · 2 comments · Fixed by #1274
Assignees
@davidpdrsn
Labels
A-axum
Milestone
0.6

Comments

@davidpdrsn
Copy link
Member

For 0.6 I wanna re-organize to changelog by grouping the changes into areas (like routing, extractors, responses, etc) and provide examples for how to migrate from 0.5 to 0.6. This should also explicitly call out subtle routing changes like the ones made in #1086
@davidpdrsn davidpdrsn added this to the 0.6 milestone Aug 11, 2022
@davidpdrsn davidpdrsn self-assigned this Aug 11, 2022
@davidpdrsn davidpdrsn mentioned this issue Aug 11, 2022
Merged
@davidpdrsn davidpdrsn changed the title Re-organize changelog to make breaking in 0.6 more clear Re-organize changelog to make updating to 0.6 easier Aug 11, 2022
@jplatte
Copy link
Member

jplatte commented Aug 15, 2022

Maybe we can also highlight that axum recently had its first birthday? 👶🏼

@davidpdrsn
Copy link
Member Author

Hehe sure!

@davidpdrsn davidpdrsn mentioned this issue Aug 18, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidpdrsn davidpdrsn

Labels
A-axum
Projects
None yet
Milestone
0.6
Development

Successfully merging a pull request may close this issue.

Re-organize changelog to make updating to 0.6 easier tokio-rs/axum
2 participants
@davidpdrsn @jplatte