-
Notifications
You must be signed in to change notification settings - Fork 114
Update roadmap after 0.5 release #243
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
Conversation
|
I do disagree with approach of brevity over everything else. This roadmap is read by a lot of people with different background (especially these days), and I vote for erring on the side of being clear and explicit with what these statements mean. (Granted, the phrasing can always be improved; I'll give it another pass.) |
We can have both. Brevity doesn't need to sacrifice clarity. Mush words don't add clarity, in fact things like "roughly" and "usually" don't add anything at all, and waste the reader's attention. |
|
Fair; I agree that one (and in particular I) should avoid weasel words. They're gone now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Except for what I commented on. Merge at will
closes #238