tqchen commented on PR #13926: URL: https://github.com/apache/tvm/pull/13926#issuecomment-1420744226
We have not yet decided on how `unity` will get merged into main. Likely the community will need to look at the unity branch as a whole to get enough context for merging into the main. It is unlikely to happen at a single point in time(or even a matter of days), or in the context of one commit. We need a long, extended period of time for branch developers to take feedback and provide examples, code tutorials, walkthroughs, and demos to get buy-in from the community. Branch development offers that flexibility and an extended period of time. Coming back to the branch establishment stage. It is indeed hard for community members who are not yet in the related code areas to be able to digest and provide feedback under the context of a single commit in the scaffolding commits. By design, scaffolding commits need a broader context that will appear in the future when connecting things together and are subject to future iterations(and rewrites in needed cases such as rebasing to main). Nevertheless, some initial agility around scaffolding commits is helpful to establish the branch and unblock developments. In the meantime, we would like to experiment with different ways to enable agility with quality. For example, encouraging community members to continue giving feedback after the merging points and requiring the merger to be responsible for reacting to these comments after the merge. Additionally, there are more valuable ways to get the community to give feedback and continuously bring iteration suggestions. We can also use forms of interaction, such as discussion posts, demos, code example walkthroughs, community meetups to get us that context through extended period of time -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
