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

Release fail 1.0 #22

Open
brson opened this issue Jan 3, 2019 · 6 comments
Open

Release fail 1.0 #22

brson opened this issue Jan 3, 2019 · 6 comments

Comments

@brson
Copy link
Collaborator

brson commented Jan 3, 2019

This can probably be done shortly after upgrading to 2018: #21

I'll probably want to clean up the documentation a bit. It's overwhelming atm.
@brson brson self-assigned this Jan 3, 2019
@brson
Copy link
Collaborator Author

brson commented Jan 3, 2019

Consider adding #23 before 1.0.

@brson
Copy link
Collaborator Author

brson commented Jan 3, 2019

Also #24.

@brson
Copy link
Collaborator Author

brson commented Jan 30, 2019

I do think #23 would be nice for 1.0 but it can always be backwards compatible later. The only thing I know I want to do for 1.0 is to make the crate docs less overwhelming (#27). I will commit to doing that this week.

@brson
Copy link
Collaborator Author

brson commented Feb 5, 2019

This needs to merge first #28

@brson
Copy link
Collaborator Author

brson commented Feb 5, 2019

As happened here don't forget to update the two docs that mention the version number.

@brson brson removed their assignment Apr 26, 2019
@brson
Copy link
Collaborator Author

brson commented Apr 26, 2019

Unassigning myself since I have not prioritized this high enough to work on. I'll keep it on my radar though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson