Skip to content

Maintain a roadmap #1917

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

Closed
gvanrossum opened this issue Jul 21, 2016 · 2 comments
Closed

Maintain a roadmap #1917

gvanrossum opened this issue Jul 21, 2016 · 2 comments

Comments

@gvanrossum
Copy link
Member

gvanrossum commented Jul 21, 2016

I found an old discussion in my inbox about a potential roadmap for mypy. Here are some excerpts:

[@JukkaL]

Moving these to the tracker sounds reasonable. One option would be to create more future milestones and add the major features to these milestones, even if they won't have any other issues until we start planning them in more detail. Maybe also add a label for important, "big rock" issues so that they won't get lost among the large number of smaller issues. For example (I haven't thought hard about which issues go into which milestones):

  • File-level flags / config file in 0.5
  • Cyclic dependency fixes in 0.5
  • Rename mypy-lang in 0.6 (or 0.5?)
  • Incremental checking on by default in 0.6
  • Plugin system in 0.7
  • Parallel checking in 0.7

We could also incorporate these in the public mypy roadmap (http://mypy-lang.org/roadmap.html).

[me]

Hm... Maybe the roadmap should move the ROADMAP.md in the GitHub repo?
We can link to it from README.md.

[@JukkaL]

That would be reasonable. That way it would be easier to update.

@gvanrossum
Copy link
Member Author

FWIW that list of "big" issues is a bit out of date:

Some new issues on the road map include:

  • make the new parser the only parser
  • strict optional checking
  • decide how to deal with bytes/str/unicode/ascii

@gvanrossum
Copy link
Member Author

This issue is not helping. Closing.

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

No branches or pull requests

1 participant