Closed #6421.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#event-3863971512
https://github.com/apache/incubator-tvm/tree/v0.7
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecomment-702882967
@comaniac cool, thanks. We plan to make a cut tomorrow.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecomment-702523862
@ZihengJiang both were merged.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecomment-702523318
> @leandron @comaniac @tqchen
> We are still waiting CI for #6597 and #6578 . I have added them into the
> release note and let's merge them tomorrow morning.
Thanks. I am actually waiting to merge them today but still waiting for their
CIs.
--
You are receiving this because you are subscribed
@leandron @comaniac @tqchen
We are still waiting CI for #6597 and #6578 . I have added them into the
release note and let's merge them tomorrow morning.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apa
> > So, #6537 and #6578 would be the final two PRs to complete the first
> > version of `tvmc`.
>
> Per offline discussion with @leandron, the final PR for TVMC would be a
> simple tutorial planned to be sent by tomorrow. We will do our best to review
> and merge them before Oct 1st.
The menti
> So, #6537 and #6578 would be the final two PRs to complete the first version
> of `tvmc`.
Per offline discussion with @leandron, the final PR for TVMC would be a simple
tutorial planned to be sent by tomorrow. We will do our best to review and
merge them before Oct 1st.
--
You are receivi
> Let us aim for Oct 1st as the tentative date for the release cutting. would
> be great to merge #6537 before then
So, #6537 and #6578 would be the final two PRs to complete the first version of
`tvmc`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email d
Let us aim for Oct 1st as the tentative date for the release cutting. would be
great to merge #6537 before then
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecommen
> TVMC(Experimental)
> * [tvmc] Introduce 'tune' subcommand (part 3/4) (#6537) -- expected to
> merge in 1 week.
> * TVMC part 4/4: Tutorial -- not filed yet but I suppose it's required if
> we list TVMC as an experimental feature in 0.7 (cc @leandron, @u99127).
@comaniac, yes, it would
@comaniac Thanks for checking! I have added missing ones except those are not
merged yet.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecomment-699131319
> 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 th
At this point, we should focus on stablization, so we don't have to rush in
features like Vitis-AI and TensorRT and we do them in v0.8 cycle(for better
stablization). We should instead list PRs that contains necessary fixes that
need to be inlcuded.
--
You are receiving this because you are
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)
* [AutoTVM][Anso
Also jump in here. 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.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitH
@apache/tvm-committers @jroesch @u99127 @comaniac
We have a release note candidate here:
https://github.com/apache/incubator-tvm/issues/6486
Please comment it if you have anything want to be added into this release or
other opinion.
--
You are receiving this because you are subscribed to th
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.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/iss
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.
--
You are receiving this because you are subscribed to
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, p
> @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/pol
@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 n
1. Is the error reporting feature included in this release as an experimental
feature or it would be in the next release?
2. For the experimental features, auto_scheduler and uTVM, would that be better
to decorate their entry points with something like `@experiment` so that it
pops a warning to
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.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://
Do we have a target date for the release?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecomment-689014924
@ZihengJiang and @zhiics have kindly agreed to serve as release managers for
this release
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6421#issuecomment-689014050
26 matches
Mail list logo
