Skip to content

Conversation

@clason
Copy link
Member

@clason clason commented Jul 17, 2021

closes #238

This was referenced Jul 19, 2021
@clason
Copy link
Member Author

clason commented Aug 27, 2021

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.)

@justinmk
Copy link
Member

justinmk commented Aug 27, 2021

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

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.

@clason
Copy link
Member Author

clason commented Aug 27, 2021

Fair; I agree that one (and in particular I) should avoid weasel words. They're gone now.

Copy link
Member

@justinmk justinmk left a 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

@justinmk justinmk merged commit 34e1b29 into neovim:master Aug 28, 2021
justinmk added a commit that referenced this pull request Aug 28, 2021
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

Successfully merging this pull request may close these issues.

Update roadmap with 0.6

2 participants