This issue is intended to give an overview, track progress and provide discussion for the roadmap of features and changes to get MicroPython to the next release.

And I'd propose that the next release be v2.0, because MicroPython is now quite mature (although definitely not finished), and also v2.0 of the software would roughly correspond to the release of pyboard v2. (See #2486 for existing discussion about v2.0.)

The following features/changes are in scope for the next release (note this list is not a guarantee, nor exhaustive):

• Python 3.5 support? and 3.6?; see #1329 and #2415
• full support for PYBD-SFx; see #4669
• initial Bluetooth support; see #4589
• integrate littlefs as a filesystem; see #5228
• support littlefs on stm32; see #3847 and #5167
• update CMSIS; see #4820
• enhance pyboard.py to copy files over serial REPL; see #4917
• remove mpy-cross from automatically being built (it's stable enough now); see #4825
• add some performance tests; see #4858
• stm32: move boards/startup*.s to stm32lib; see 6b6403ce76e11fd564d9bbe90f190c99fe4e4fa2
• stm32: multi LUN support on USB MSC; see 53200247b779358ffa03e1b7a8d1e9964befc234
• add I2CSlave support (I2CSlaveFIFO, I2CSlaveMem)
• esp8266/esp32: switch to use LittleFS (saves 4k RAM, more robust filesystem)?
• esp32: support more of its features, like OTA, mesh, I2S
• esp32: support for SDCard; see #4772
• esp32: support for hardware I2C; see #4914
• initial port to ATSAMDx MCUs; see #4863