Open ysh329 opened 10 months ago
Hi all, make version modification twice as two commits in one PR merged (https://github.com/apache/tvm/pull/16326). We need:
I don't know how to push tags/branch created on my own repo to apache/tvm's? I didn't find about create branch by Web UI as below in apache/tvm:
Hi all, make version modification twice as two commits in one PR merged (#16326). We need:
- Create a branch named v0.15.0 from main on first commit(7445b87);
- Create a tag named v0.15.0.rc0 on first commit(7445b87);
- Create a tag named v0.16.dev0 created on second commit(e69363a).
I don't know how to push tags/branch created on my own repo to apache/tvm's? I didn't find about create branch by Web UI as below in apache/tvm:
Besides, I push tags and branch created by command line to my own repo. However, I don't know how to push to apache/tvm.
cc @Hzfengsy @vinx13 @tqchen
@ysh329 a tag will be created automatically if you create a release on GitHub
@ysh329 a tag will be created automatically if you create a release on GitHub
I found this Create a new release link in my own tvm repo:
but find nothing link about Create a new release below apache/tvm repo:
cc @Hzfengsy @vinx13
@ysh329 you may need to setup your github account following https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer
@ysh329 you may need to setup your github account following https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer
Oh, u r right.
Hi all, may delay few days, may some issue when I register iCLA previous. I resend a register email. If anyone has cherry-pick PR, please notify in this thread.
Hi all, make version modification twice as two commits in one PR merged (#16326). We need:
Hi all, branch and tags created.
Hi all, due to cherry-pick PR about release signing, I update the tag v0.15.0.rc0 to new commit: a340dbed7353a5ef24e72b73fe8fff3665f3359a.
Hi all, vote starts (https://github.com/apache/tvm/issues/16428). Everyone is welcomed to vote. Please vote by replying to this thread (https://github.com/apache/tvm/issues/16428) explicitly. Vote will close Jan. 25th at 23:59M GMT.
Hi all, github tag v0.15.0 created and release page updated. Please help update apache svn repo, because it need authority:
After the vote passes, to upload the binaries to Apache mirrors, you move the binaries from dev directory (this should be where they are voted) to release directory. This “moving” is the only way you can add stuff to the actual release directory. (Note: only PMC can move to release directory) From doc about post the release: https://tvm.apache.org/docs/contribute/release_process.html?highlight=release#post-the-release
cc @Hzfengsy @junrushao @tqchen
I didn't find doc link from CI in last PR (https://github.com/apache/tvm/pull/16424): https://ci.tlcpack.ai/blue/organizations/jenkins/tvm-arm/detail/PR-16424/1/pipeline, can u give me some prompt @vinx13
This schedule is tentative and may change as we progress through the process. In case dates change, this thread will be kept updated.
The proposed schedule is:
v0.15.0
on main branch; second tov0.16.dev0
on main branch in one PR, and merged without squash (required). Why do this first referring discuss on v0.14.0 release: https://github.com/apache/tvm/pull/16326v0.15.0
to be created frommain
on first commit: https://github.com/apache/tvm/tree/v0.15.0v0.15.0.rc0
created on first commit: https://github.com/apache/tvm/releases/tag/v0.15.0.rc0v0.16.dev0
created on second commit: https://github.com/apache/tvm/releases/tag/v0.16.dev0v0.15.0.rc0
and uploadingv0.15.0.rc0
: https://github.com/apache/tvm/releases/tag/v0.15.0.rc0v0.15.0
on last commit on release branch: https://github.com/apache/tvm/releases/tag/v0.15.0Call for release managers: In case you want to be involved in upcoming releases, please manifest your interest in this thread and we'll try to organise. 😆
See also:
cc @apache/tvm-committers @Hzfengsy @vinx13 @areusch @Mousius @tqchen @AndrewZhaoLuo @Johnson9009