Can we cherry pick #14538 as well?
more context: https://github.com/apache/tvm/pull/14715#issuecomment-1522533241
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14505#issuecomment-1522533737
You are receiving this because you are subscribed to this thr
Yeah this is a CI problem, I think we should just disable that behavior for
releases, I filed a PR to do it: #14714. Once that is merged into v0.12.0, we
can rebase this PR and it should use the updated CI configs
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/t
Merged #14653 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/14653#event-9043384427
You are receiving this because you are subscribed to this thread.
Message ID:
> Hi @driazati I'm recently prepraing the release note, but I met a problem
> after create csv files. My step is following
> [readme](https://github.com/apache/tvm/blob/main/tests/scripts/release/README.md),
> it mentions below:
>
> > You can then import thi
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14260#issuecomment-1469058137
You are receiving this because you are subscribed to this thread.
Message ID:
The version numbers should reflect the current version (and it's in more places
than `version.py`). There should be a PR against the v0.11.0 branch like #12190
that updates the version numbers from `v0.11.0` to `v0.11.1`, then we tag that
commit once it's merged as the new v0.11.1
--
Reply to
Checked building with [this
config](https://github.com/tlc-pack/tlcpack/blob/main/wheel/build_wheel_manylinux.sh#L88)
minus `ETHOSN` and `ETHOSU` and it seems to import correctly and
`typing_extensions` is installed during a `pip install`. As @Johnson9009
pointed out though the rc package will
the failure I think is because the `/` in the branch name is getting used in
the docker tag, I pushed a fix to strip them out (but if it persists we can
just merge this and proceed with the release since the docker builds aren't
really consequential)
--
Reply to this email directly or view it
> Looks like the GH branch protection is kicking in , kind of like :
> https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging
>
> Alternatively, you
The release branches are protected from force pushes / deletes by GitHub, but
cherry-picking shouldn't require rewriting history right? Are you doing
something like this?
```bash
git fetch origin
git checkout v0.11.0
git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
git push origin
```
-
Closed #12181 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12181#event-7828259338
You are receiving this because you are subscribed to this thread.
Message ID:
Closing since the PR is merged, we can re-open if need be
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12181#issuecomment-1317720287
You are receiving this because you are subscribed to this thread.
Message ID:
This is mostly to address https://github.com/tlc-pack/tlcpack/issues/149
and make it clear how to avoid that in the future.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/13351
-- Commit Summary --
* [docs] Add some more release process doc
This reverts commit 5acf3f90c63b6760cd23796b442f8ac20e645af0.
Reverting since this is causing some spam from the ASF Infra bot related
to https://issues.apache.org/jira/browse/INFRA-23834. As in that issue
the protections have been applied manually by ASF Infra so this revert
shouldn't have any re
Merged #13208 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/13208#event-7685020248
You are receiving this because you are subscribed to this thread.
Message ID:
This adds a fnmatch entry for the release branches to ensure that
changes come from PRs and that force pushes / rebased aren't allowed so
it's always possible to trace the release branch back to a mainline TVM
commit.
You can view, comment on, or merge this pull request online at:
https://github
Merged #13141 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/13141#event-7625211200
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #13106 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/13106#event-7613494103
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #13025 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/13025#event-7564645426
You are receiving this because you are subscribed to this thread.
Message ID:
+1, checked the gpg signature and build, all looks good!
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/13026#issuecomment-1274948163
You are receiving this because you are subscribed to this thread.
Message ID:
tion may use the work "sign
> off", the full test suite will be confirmed to meet the release requirement.
> My question is that do we have the extra "sign off" testing? @AndrewZhaoLuo,
> @driazati, @tqchen Thanks.
Everything that we currently test is run on every c
Closed #12133 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12133#event-7398834774
You are receiving this because you are subscribed to this thread.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12743#issuecomment-1241264017
You are receiving this because you are subscribed to this thread.
Message ID:
> @driazati notes that GitHub [just
> introduced](https://github.blog/changelog/2022-08-23-new-options-for-controlling-the-default-commit-message-when-merging-a-pull-request/)
> new options for controlling the default commit messages, so hopefully we can
> leverage that to impleme
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12583#issuecomment-1226556624
You are receiving this because you are subscribed to this thread.
Message ID:
> i would love for tvm-bot to enforce this
We can also enforce whatever rules as part of lint, #12367 has an example
implementation for what we could do
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#issuecomment-1220859744
You are receiving thi
> Moreover, because typically (in GH for instance) the PR (title and body) is
> auto-generated from the initial commit messages, if you apply the guidelines
> to these commits you kill two birds with one stone: you get a nice PR "for
> free" and also help the review.
(this isn't really a commen
Finally posted announcement in
https://discuss.tvm.apache.org/t/apace-tvm-v0-9-0-release/13291
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#issuecomment-1208522099
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #11736 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#event-7149769797
You are receiving this because you are subscribed to this thread.
Message ID:
This release and past releases have included the `rc0` in the top-level folder
inside the source release tar. We've pushed a [new
RC](https://dist.apache.org/repos/dist/dev/tvm/tvm-0.9.0-rc1/) with all the
contents the same except the top level folder, which is named the same thing
without the
Thanks everyone! Following the schedule in #11736 the vote thread is closing
today with the results in #12133.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12103#issuecomment-1189295436
You are receiving this because you are subscribed to this thread
Closed #12103 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12103#event-7022208825
You are receiving this because you are subscribed to this thread.
Message ID:
Closing now that the vote thread has passed: #12133
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12102#issuecomment-1189293781
You are receiving this because you are subscribed to this thread.
Message ID:
Dear TVM community,
I'm glad to announce the results of the vote for the release of the v0.9.0.rc0
package. This vote passes with 6 +1 votes 4 binding), no 0 votes, and 0 -1 vote.
+1 votes
- Christopher Sidebottom
- Cody Yu (binding)
- Jared Roesch (binding)
- Masahiro Masuda (binding)
- Tianqi
# Introduction
The TVM community has worked since the v0.8 release to deliver many exciting
features and improvements. v0.9.0 is the first release on the new [quarterly
release](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md)
schedule and includes many highlights,
Dear TVM community,
This is a call for vote to release Apache TVM version v0.9.0. This is a major
release with many new features and improvements. All users of Apache TVM v0.8
are advised to upgrade. Please see #12102 for any edits you would like to see
included in the release notes.
Link to
**Please leave any comments or edit this issue directly to adjust the release
notes. Also see the rc0 vote thread #tbd**.
# Introduction
The TVM community has worked since the v0.8 release to deliver many exciting
features and improvements. v0.9.0 is the first release on the new [quarterly
rel
Yeah, along with some other things but #12022 is the only remaining item
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#issuecomment-1184685291
You are receiving this because you are subscribed to this thread.
Message ID:
it ignores any extra images that someone might manually push (or the validated
ones that get pushed by ci with the name `123-123-abc-validated`)
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11938#issuecomment-1183584180
You are receiving this because y
Merged #11992 into v0.9.0.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11992#event-6988495839
You are receiving this because you are subscribed to this thread.
Message ID:
failures look flaky, merging anyways
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11992#issuecomment-1183580209
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #12076 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/12076#event-6981394712
You are receiving this because you are subscribed to this thread.
Message ID:
As per https://tvm.apache.org/docs/contribute/release_process.html#id3
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/12076
-- Commit Summary --
* [COMMUNITY] Add driazati key for release
-- File Changes --
M KEYS (48)
-- Patch
Merged #11991 into v0.9.0.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11991#event-6980196703
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #11989.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11989#event-6920928075
You are receiving this because you are subscribed to this thread.
Message ID:
moved to a branch build for Jenkins' sake in #11992
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11989#issuecomment-1172694744
You are receiving this because you are subscribed to this thread.
Message ID:
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/11992
-- Commit Summary --
* [release][v0.9] Remove VTA submodule
-- File Changes --
M .gitmodules (3)
D 3rdparty/vta-hw (1)
M CMakeLists.txt (2)
M Jenkinsfile (128)
M je
Closed #11990.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11990#event-6920360743
You are receiving this because you are subscribed to this thread.
Message ID:
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/11991
-- Commit Summary --
* [release] Bump version numbers to v0.9.0
-- File Changes --
M NOTICE (2)
M conda/recipe/meta.yaml (2)
M include/tvm/runtime/c_runtime_api.h (2)
M
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/11990
-- Commit Summary --
* [release] Bump version numbers to v0.9.0
-- File Changes --
M NOTICE (2)
M conda/recipe/meta.yaml (2)
M include/tvm/runtime/c_runtime_api.h (2)
M
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/11989
-- Commit Summary --
* [release][v0.9] Remove VTA submodule
-- File Changes --
M .gitmodules (3)
D 3rdparty/vta-hw (1)
-- Patch Links --
https://github.com/apache/tvm/pull/11
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/11987
-- Commit Summary --
* [release] Add script to gather PRs for a release
-- File Changes --
A tests/scripts/gather_prs.py (179)
-- Patch Links --
https://github.com/apache/tvm/pul
cherry pick: #11969
reason: needed to get tests on the Python wheel in GitHub Actions passing
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#issuecomment-1171615115
You are receiving this because you are subscribed to this thread.
Message ID:
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/11938
-- Commit Summary --
* [ci][docker] Use RFC image tags only
-- File Changes --
M tests/scripts/open_docker_update_pr.py (6)
-- Patch Links --
https://github.com/apache/tvm/pull/1
v0.9.0 has been cut at 97b3076c3532f73a9d9eeba26a3f329f8e0f803d in
https://github.com/apache/tvm/tree/v0.9.0
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#issuecomment-1169049639
You are receiving this because you are subscribed to this thread.
As discussed in
https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md,
we will be publishing a release of TVM on mid July. We will do a branch cut
soon but accept cherry-picked changes for a couple weeks. See the [release
steps](https://github.com/apache/tvm-rfcs/blob/mai
Discussion in the community meeting was pretty supportive! Some summary notes:
* Name prefix option makes sense, change seems like a natural evolution of MLF
* Before users would have to do the same thing by hand
* Is the deserializer going to be backwards compatible?
* No loader in C++ runtime,
Yeah that index was down for a while last week
(https://github.com/apache/tvm/pull/11156#issuecomment-1112015086) but it
should be working now. If this happens again we might want to look into
rehosting some of those assets
--
Reply to this email directly or view it on GitHub:
https://github.c
thanks for summarizing the meeting! I agree with @areusch's points on support
and have added some text about it
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/67#issuecomment-1124178464
You are receiving this because you are subscribed to this thre
I agree with @areusch that a lot changes pre and post 1.0. This RFC's main
focus is getting code out the door often, so with that I think it makes the
most sense to only support the current version and only publish a new release
mid-cycle for critical bug fixes and security issues.
Ostensibly t
[quote="gromero, post:8, topic:12334"]
I think the onus should *not* be on the reviewers, and I think that an ask like
that would avoid it: it’s a submitter’s duty to write a good commit message,
just like a correct/good code.
[/quote]
I definitely agree we should try these suggestions and add
[quote="manupa-arm, post:5, topic:12047"]
I am not sure I follow this proposal. Can you elaborate ?
[/quote]
It's mostly that we trust all code running on a branch but not necessarily code
running from PRs from forks, same as how Jenkins treats the `Jenkinsfile`
today. After thinking about thi
[quote="areusch, post:4, topic:12220"]
committers have reviewed and one wants to approve the PR but not merge it until
the others have looked the PR over.
[/quote]
One of the main reasons of this work would be to explicitly remove this step,
though it makes sense to still limit the ability to
# [RFC] Merge Bot
## Summary
PRs authors must currently wait for changes to be manually merged by a
committer clicking the "merge" button. A large amount of time can often elapse
between CI going green, a PR being approved, and this merge button being
pressed. This RFC proposes a safe, self-
TVM has two methods of user engagement today:
* GitHub [PRs](https://github.com/apache/tvm/pulls) and
[Issues](https://github.com/apache/tvm/issues)
* The [Discuss forum](https://discuss.tvm.apache.org/)
Historically both GitHub and Discuss have been used to develop on TVM, with
design discus
Posted the https://github.com/apache/tvm-rfcs/pull/58 with some links to PRs
that should address some of the concerns.
---
[Visit Topic](https://discuss.tvm.apache.org/t/rfc-remove-codeowners/12095/13)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscri
iefly inspect the PR topic / changes and assign reviewers directly / tag
people via `@`-ing them
* Add the `triaged` label
[quote="areusch, post:7, topic:12095"]
I really like this idea. @driazati do you think this would be a big change?
seems like it’s pretty related to the PR ping bot.
[
It was brought up that it would be nice to have the ability to not only cc
specific people as reviewers but groups of people by labels. PyTorch does
something [similar](https://github.com/pytorch/pytorch/issues/24422) which we
could mostly copy. So labels could be automatically assigned based
Running arbitrary commands directly on the node is already possible in several
places in the `Jenkinsfile`:
* https://github.com/apache/tvm/blob/main/Jenkinsfile#L97
* https://github.com/apache/tvm/blob/main/Jenkinsfile#L127
* https://github.com/apache/tvm/blob/main/Jenkinsfile#L167
So our secu
# **Summary**
Move `.github/CODEOWNERS` to `.github/CODEOWNERSHIP` to avoid triggering
GitHub’s [automatic review
requests](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#about-code-owners).
Add GitHub Acti
# Summary
Rebuild Docker images per-build rather than use the pinned Docker Hub images in
the [Jenkinsfile](https://github.com/apache/tvm/blob/main/Jenkinsfile#L48-L54).
# Guide
Note: This is a spin off discussion from
[https://discuss.tvm.apache.org/t/rfc-a-proposed-update-to-the-docker-ima
On the implementation side a bot (likely this new one:
https://github.com/tvm-bot) with triage-level permissions could ensure that
`[skip ci]` is present in the PR title if any of the commits in the PR have
skipped CI (if a commit comes later on where CI isn't skipped, the submitter
can manua
72 matches
Mail list logo
