[Release] v0.8 Release Planning

[junrushao]

Thanks to everyone who contributed in the past cycle! We would love to use this thread to plan for the v0.8 release. The community has always been focusing on high quality releases. This process can take several weeks according to past releases, to allow us to collectively work together on items and track things that needs to be merged.

In the next few days we will be populating the release note in this thread. Most release note content will be derived from our monthly report.

@vinx13 and I volunteered to manage the release, and @icemelon and @yzhliu will mentor us as PMC members.

Please don't hesitate to share your thoughts :-)

[leandron]

Thanks for doing this work! There were some items listed on #7434, perhaps we can start with those?

[Hzfengsy]

Thanks for the work. I believe v0.8 is a good chance to land TensorIR scheduling (#7527). Also, I will try my best to contribute some initial TensorIR tutorials and documentations before the v0.8 release.

[comaniac]

Agree with @leandron that we could firstly refer to the items there. Many "initial" features in v0.7 are now stable. For example:

• Initial automatic scheduling support -> stable.
• Initial command line driver interface -> stable.
• Intial Hexagon support -> stable.
• Bring your own codegen (BYOC) support -> now we have several backends.
  • [stable] NVIDIA TensorRT, Xilinx Vitis-AI, ARM compute library, ARM Ethos-N, etc.
  • [experimental] TBA.

[junrushao]

I wanted to propose as a highlight the TE-level auto-differentiation work, lead by @yzhliu, which unlocks TE-level training capability in the TVM stack

[KaiyangQ99]

Expecting the new release!

[FrozenGene]

Agree with @leandron that we could firstly refer to the items there. Many "initial" features in v0.7 are now stable. For example:

* Initial automatic scheduling support -> stable.

* Initial command line driver interface -> stable.

* Intial Hexagon support -> stable.

* Bring your own codegen (BYOC) support -> now we have several backends.
  
  * [stable] NVIDIA TensorRT, Xilinx Vitis-AI, ARM compute library, ARM Ethos-N, etc.
  * [experimental] TBA.

Does our hexagon support is stable now? I am not sure about it. As I saw we still pull requests actively(like #8986 to support model lauch). I think the status maybe is still not stable. @kparzysz-quic should give more definitive answer

[kparzysz-quic]

Hexagon support still needs more work.

[areusch]

Just checking--by "stable" for the "command line driver interface," does that mean "someone should write a script and presume we won't change the command syntax?"

For µTVM we could add:

• microTVM Project API -> initial support
• microTVM AOT executor -> initial support
• microTVM platforms: Zephyr, Arduino -> initial support

I'd like us to avoid using "uTVM" to refer to microTVM in the release notes and just spell out the word "micro" instead. While u is still a common abbreviation for mu, it's not necessarily widely known. We've renamed most occurrences of uTVM inside the codebase to avoid confusion.

[junrushao]

@vinx13 and I spent the previous 2 weeks categorizing the 69 pages of changelogs via git commits: https://docs.google.com/document/d/1D2rig32yZ4H48_tXHb_svnPnt4-FRx3JUbBxKyrW_-I/

Below are the categories we are using:

• TE, TIR, TVMScript
• AutoTVM, AutoScheduler, Meta Schedule
• Operator Coverage
• Training
• Relay
• MicroTVM, AOT, Graph Executor and VM
• Arithmetic Analysis
• Frontends
  • PaddlePaddle
  • ONNX
  • TensorFlow, TFLite
  • PyTorch
  • MXNet
  • Misc
• Codegen Backends and Runtime
  • LLVM
  • ROCm
  • Vulkan, SPIR-V
  • Metal
  • OpenCL, VTA, Vertilator
  • CUDA
  • ARM
  • Hexagon
  • WASM
  • C
• BYOC Integration with Vendor Libraries: TensorRT, ACL, VitisAI
• TVMC
• Rust and Other Language Binding
• Documents, Tutorials
• CI, Docker, Build, Test
• Misc
  • RPC
  • Target
  • Community
  • Other changes

Please feel free to suggest in the doc if there is any mistake :-)

[areusch]

@junrushao1994 what's the status of the release? is there a list of issues that need to be resolved before we cut?

also cc @denise-k @Mousius @mbs-octoml

[junrushao]

@areusch thanks for asking! sorry I was in vacation by the time of the post.

@vinx13 and I are actively drafting a release note, and will cut a release candidate by next Monday (Nov 1, 2021); After that, there is an extra week for feedbacks (until Nov 8, 2021).

If there is any small commit after Monday that needs to be included in the RC, please let us know in this thread, as long as it's not a last minute breaking change

[Mousius]

@junrushao1994 does this mean that 0.8 will go out with half finished implementations for things, such as library integrations (i.e. CMSIS-NN) and tvmc arguments (tvmc is not yet stable as there's breaking changes incoming)? If the process is just to take main and tag it, can we rapidly move to focusing on a 0.9 release with a list of issues as suggested by @areusch so we can work towards stability in a 1.x release.

[jiangjiajun]

Hi, @junrushao1994
I think we could add paddlepaddle frontend as a new feature in the release note of v0.8