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 Discussion of Python 3.5 support #1329 and Discussion of Python 3.6 support #2415
• full support for PYBD-SFx; see stm32: Add support for PYBD boards #4669
• initial Bluetooth support; see Cross-platform Bluetooth support #4589
• integrate littlefs as a filesystem; see vfs: add littlefs v1 and v2 bindings #5228
• support littlefs on stm32; see Add littlefs component, with submodule and VFS bindings (WIP) #3847 and LittleFS Filesystem Support #5167
• update CMSIS; see lib/cmsis: Upgrade to CMSIS 5.5.1. #4820
• enhance pyboard.py to copy files over serial REPL; see tools/pyboard.py: Add filesystem commands to ls/cat/cp/rm remote files. #4917
• remove mpy-cross from automatically being built (it's stable enough now); see mpy-cross: Do not automatically build mpy-cross, rather do it manually. #4825
• add some performance tests; see tests: Add performance benchmarking test suite. #4858
• stm32: move boards/startup*.s to stm32lib; see 6b6403c
• stm32: multi LUN support on USB MSC; see 5320024
• 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 Support for hardware SD/MMC access on ESP32 #4772
• esp32: support for hardware I2C; see esp32: Add support for hardware I2C. #4914
• initial port to ATSAMDx MCUs; see Add new port to Microchip SAMD microcontrollers #4863