-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[RFC] v0.7 Release Planning #6421
Comments
@ZihengJiang and @zhiics have kindly agreed to serve as release managers for this release |
Do we have a target date for the release? |
Of course the the date would depends on the status of the release, because we should always aim for quality. Based on our past experience, it might takes a few weeks. |
|
@comaniac if we land the final error reporting PR it removes the existing error reporting from type checker completely, I think we should either choose to ship it this release or delay until next release. One worry is that there will probably be a period of stability where we iterate/polish on new errors. |
Make sense to me (including the worry as well). Different from auto_scheduler and uTVM, error reporting is not just a standalone module that users can completely ignore, so we should be more careful. |
I agree that we should mark certain features as initial support/experimental in the release note. We could also come up with documentation tags to mark the feature as experimental. I am less certain sure about shooting a warning for each function call, as they harm the overall user experience, perhaps we can start with the release note and docs? |
Yeah, I also prefer to document it instead of throwing many warnings. In addition, we have some checker in the codebase claiming that some APIs will be deprecated in the next release. We probably want to take some actions on them as well. |
I'd like to see the tvmc work to be functional before we cut the release please. I'd also like to see the Ethos-N PRs land as well. |
Let us plan to cut a release next week. At this point we should consider "freeze the features", but please suggest a list of PRs(fixes) that need to be merged. |
A brief summary of the related PRs missed in the current release note candidates. Not sure if all of them have to be listed so just for reference. Except for the note followed by the PR indicating its status, all PRs listed here are merged. Automatic Scheduling (Experimental)
BYOC
TVMC(Experimental)
|
At this point, we should focus on stablization, so we don't have to rush in features like Vitis-AI and TensorRT and can do them in the v0.8 cycle(for better stablization). We should instead list PRs that contains necessary fixes that need to be inlcuded. |
Make sense. Removed them from the list. |
@comaniac Thanks for checking! I have added missing ones except those are not merged yet. |
@comaniac, yes, it would be great to merge #6537 before the release, lets try to solve all the issues early next week; Also, "part 4/4", related to |
Let us aim for Oct 1st as the tentative date for the release cutting. would be great to merge #6537 before then |
The mentioned tutorial PR is #6597 |
@ZihengJiang both were merged. |
@comaniac cool, thanks. We plan to make a cut tomorrow. |
Thanks to everyone who works hard in the past cycle. This RFC to plan for v0.7 release. The community has always been focusing on high quality releases.
One of the major highlights in the past cycle is that we have gone through major refactors to make sure we have a fresh new foundation for new things we want to develop, and there are also exciting new features such as auto scheduler and uTVM coming in.
Considering the nature of the new foundational change, we propose to focus of this release on landing key foundational changes we have made -- for example the new TIR/target and pass infra, since they affect the API itself.
Because we are landing new features at a fast pace, we might include experimental features(that does not affect API itself) that may still need stabilization and work to cut another release after these features stabilize. We would include auto_scheduler(ansor) and intitial uTVM would be part of this release as experimental features and we will continue to polish the features in the incoming cycle.
Please share your thoughts.
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.
The text was updated successfully, but these errors were encountered: