ysh329 commented on issue #15134: URL: https://github.com/apache/tvm/issues/15134#issuecomment-1607649151
> Can below two steps be merged into one? Because these steps have some relationship, i.e., the commit of "v0.14.dev0" must be the next commit of branch v0.13.0, in addition these two steps can be done quickly as long as the contributor has enough permission. > > > 1 July 2023 - a branch v0.13.0 to be created from main > > 3 July 2023 - a tag v0.14.dev0 to be created, marking the beginning of the next development cycle > > In addition, there need add another step for modifying the version recorded in main branch code to "v0.14.dev0", because this step need to send a PR and need run all tests, so it maybe need 1~2 days to be merged. Good question. I checked recently commit history records about `0.xx.dev0` on main branch and found the next submission of tagged `0.xx.dev0` were not PR changed version, which were non-standard. I think these two things about `a branch v0.13.0 to be created from main` and `a tag v0.14.dev0 to be created` can be merged. Of course, **the next submission of tagged `0.xx.dev0`** should be the PR modifying the version recorded like [this](https://github.com/apache/tvm/pull/14544/files). I modified the schedule and add a step about `modifying the version recorded in main branch code to "v0.14.dev0"`. -- 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]
