the timeline looks good to me, we do need someone to serve as release manager.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14505#issuecomment-1500559130
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/14260#issuecomment-1470304216
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/14260#issuecomment-1468974281
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #14300 into v0.11.0.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/14300#event-8749210368
You are receiving this because you are subscribed to this thread.
Message ID:
@leandron i think that PR should unblock the release
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14260#issuecomment-1468882801
You are receiving this because you are subscribed to this thread.
Message ID:
okay i took a look here and i think something is messy with our process. here
is the process now:
1. cut a release branch, then update the checked-in version strings by running
`python3 version.py`, then creating a PR out of the diff. that typically should
look like https://github.com/apache/tvm
-1
yeah agreed we should fix the version numbering first before releasing, sorry i
forgot to check that. -1 til we do that.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14260#issuecomment-1464639756
You are receiving this because you are subscribed
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14260#issuecomment-1462781749
You are receiving this because you are subscribed to this thread.
Message ID:
Unfortunately I encountered a problem when trying to publish the wheels for
v0.11.0:
```
$ venv/bin/python3
Python 3.8.10 (default, Nov 14 2022, 12:59:47)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tvm
Traceback (most recent call last):
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14129#issuecomment-1445433214
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #14121 into v0.11.0.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/14121#event-8607371227
You are receiving this because you are subscribed to this thread.
Message ID:
just noting that i think the docker build failure is unrelated here
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/14121#issuecomment-129403
You are receiving this because you are subscribed to this thread.
Message ID:
This PR switches to using `env.CHANGE_ID` to identify whether we are building a
PR. It also uses `CHANGE_TARGET` instead of hardcoding `main` check in
Prepare.groovy. Let's merge this to v0.11.0 release branch where there are
CI problems first, then we can cherry-pick to main via another PR.
@d
0
Ultimately I'd prefer to get more clarity on this direction, but given we are
getting that through the new `unity` branch, it makes sense to adopt this
proposal as the "goal" given that progress on the unity branch will further
illuminate the details.
--
Reply to this email directly or view
okay, traced this down with the help of asf infra. it appears we tried to
configure this in `.asf.yaml` last Oct, but GH API didn't support configuring
branch patterns. @driazati filed a
[ticket](https://issues.apache.org/jira/browse/INFRA-23834) about this and they
manually configured it for u
i have [asked](https://the-asf.slack.com/archives/CBX4TSBQ8/p1675409181932449)
asf-infra whether perhaps gitbox has misconfigured our branch protection. i'm
not able to view that natively in the GH UI, i believe, so i'm left to deduce
what i can from the asf.yaml and associated docs.
--
Reply
cc @kparzysz-quic @alter-xp @philippvk
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/98#issuecomment-1402807746
You are receiving this because you are subscribed to this thread.
Message ID:
we discussed the release in the community meeting this morning. here are notes:
- release is running late. @leandron will update the schedule
- branch created, current status is past the hard deadline for cherry-picks.
can still get a few last commits in given we are behind (but speak up soon).
-
I appreciate you guys bringing this back up, and I appreciate the goal here of
establishing a project policy to ensure we're welcoming to new projects as the
MLC landscape changes. I still have some reservations about this proposal in
its current form, but I would support it if a small number of
sorry for the long delay in review, I've been on holiday for a while now. I'll
take a look over this.
cc @mehrdadh @alanmacd @mkatanbaf
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1324139260
You are receiving this because you are
I'm going to close this issue since there hasn't been any change in a couple
years. Feel free to reopen if needed. The Discourse forum is a good place for
questions like this too.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/2975#issuecomment-131770
Closed #2975 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/2975#event-7828180890
You are receiving this because you are subscribed to this thread.
Message ID:
@Hzfengsy
> Note that the reviews of each PR are brought to their own context, and we
> anticipate grounded constructive actionable comments, such as adding test
> coverage here/there. The module establishment part can be into subjective
> discussions that are less grounded, and community empo
thanks for the replies here, everyone.
@comaniac
>-1 is totally fine and I don't think this Process RFC forbids this. On the
>other hand, if an RFC is suspensive for a while but we still cannot make every
>-1 voter happy, it doesn't make sense to me to reject the RFC (we don't
>actually "reje
these two volunteered to help triage issues per [Issue Triage
RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0093_Issue_Triage.md).
@tqchen @driazati
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm/pull/13141
-- Commit Summary --
* [sk
Merged #12988 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/12988#event-7603312808
You are receiving this because you are subscribed to this thread.
Message ID:
+1. checked tarball prefix directory name and i don't see any changes to
3rdparty directory.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/13026#issuecomment-1274248049
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #12898 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/12898#event-7520335399
You are receiving this because you are subscribed to this thread.
Message ID:
if it's not too late, could https://github.com/apache/tvm/pull/12856 get
cherry-picked as well?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12832#issuecomment-1261485570
You are receiving this because you are subscribed to this thread.
Message ID:
#12880 is ready to cherry-pick
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12832#issuecomment-1261437911
You are receiving this because you are subscribed to this thread.
Message ID:
I'm hoping to land https://github.com/apache/tvm/pull/12880 shortly, will
update this thread when it does so we can cherry-pick it.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12832#issuecomment-1258419300
You are receiving this because you are subs
### This issue is to track progress for [Issue Tracking
RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0093_Issue_Triage.md).
This issue has these tasks:
- [ ] Create labels described in the RFC.
- [ ] Modify ISSUE_TEMPLATES to remove Update CI Docker Image issue template
and add `needs
Merged #93 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/93#event-7398602530
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #12743 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12743#event-7398501058
You are receiving this because you are subscribed to this thread.
Message ID:
The vote period has concluded. The votes are as follows:
+1
Tristan
David
Leandro
Wuwei
Gustavo
Masa
Chris S.
Xiyou
TQ
Andrew
0:
none
-1:
none
The vote has passed, and the RFC is accepted. Thanks everyone!
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/iss
+1 (binding)
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12743#issuecomment-1248657387
You are receiving this because you are subscribed to this thread.
Message ID:
This is a formal vote thread to determine committer and PMC support for
https://github.com/apache/tvm-rfcs/pull/93. Replying +1 here means you support
the RFC and we should merge it. This vote thread is due to the fact that the
RFC proposes a change in the way the community operates (namely the
cc @apache/tvm-committers I'll probably send this for a vote in 1 or 2 days
since it's been active on the discuss forum for a week without comment. Please
take a look.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/93#issuecomment-1239949445
You ar
same. maybe upstream?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12703#issuecomment-1239829977
You are receiving this because you are subscribed to this thread.
Message ID:
looking at this one as it's blocking #12663 too.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12703#issuecomment-1238388683
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #88 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#event-7300385635
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #12583 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12583#event-7300381798
You are receiving this because you are subscribed to this thread.
Message ID:
The vote has passed, therefore I'll merge this RFC. @gromero please create a
tracking issue (you can create another PR to add it to this doc).
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#issuecomment-1233535253
You are receiving this because y
The 7-day voting period has concluded. The votes are as follows:
+1:
Leandro
Thierry
Chris Sullivan
TQ
David
Siyuan
Junru
Masa
Manupa
Luke
Matthew Barrett
Eric Lunderberg
0:
Andrew Luo
Krzysztof
Xiyou
-1:
none
The vote has passed.
--
Reply to this email directly or view it on GitHub:
https://
-1 (binding veto)
I agree with @leandron that Establish TVM Unity Connection Technical Strategy
RFC is heavily centered around Relax RFC. Additionally, while this RFC stops
short of endorsing the Relax RFC as the future direction of TVM, it very
[explicitly
discusses](https://github.com/apache
I created a [vote thread](https://github.com/apache/tvm/issues/12583) to
broadcast this more broadly to the community. Please signal your support there.
@driazati notes that GitHub [just
introduced](https://github.blog/changelog/2022-08-23-new-options-for-controlling-the-default-commit-message-
This is a formal vote thread to determine committer and PMC support for
https://github.com/apache/tvm-rfcs/pull/88. Replying +1 here means you support
the RFC and we should merge it. This vote thread is due to the fact that the
RFC proposes a change in the way the community operates (namely the
Merged #78 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/78#event-7234944888
You are receiving this because you are subscribed to this thread.
Message ID:
@junrushao1994 i would love for tvm-bot to enforce this as much as possible.
some items are going to be more challenging than others. the thing i think we'd
really like is for tvm-bot to handle merging, so that we consistently remember
to copy the PR body into the git commit body. we've been deb
@gromero thanks for sending the RFC! let's leave it open for a few days for
discussion, then I will create a `[VOTE]` GH issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#issuecomment-1215326331
You are receiving this because you are subscrib
Merged #11987 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11987#event-7114066219
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #71 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/71#event-7112016296
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #11938 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11938#event-7076836620
You are receiving this because you are subscribed to this thread.
Message ID:
thanks @gigiblender , the RFC has been accepted! please create a [tracking
issue](github.com/apache/tvm/issues) and mention this PR in that issue to link
it.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/84#issuecomment-1194446926
You are receivin
Merged #84 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/84#event-7058767959
You are receiving this because you are subscribed to this thread.
Message ID:
@gigiblender is this ready for a last review?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/84#issuecomment-1193602324
You are receiving this because you are subscribed to this thread.
Message ID:
@gigiblender could you review this one so you can understand how this tool
works?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11938#issuecomment-1193593317
You are receiving this because you are subscribed to this thread.
Message ID:
@Mousius want to make the other suggested updates? then I'm good with this RFC
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/71#issuecomment-1193570733
You are receiving this because you are subscribed to this thread.
Message ID:
just to update this issue, we're nearly done cutting the release and will post
the release announcement shortly. we had a hiccup with our schedule here.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#issuecomment-1193565005
You are receiving this
+1 to this as well, i will leave the previously-approved rc0 in the release dir
for posterity.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12103#issuecomment-1189443940
You are receiving this because you are subscribed to this thread.
Message ID:
we discussed this at the [community
meeting](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-july-13/13120/2)
yesterday. here are notes:
- @areusch: one of suggestions raised was to make it possible to reconstruct a
NameSupply from an IRModule. we might need to make it possible to i
@kparzysz-quic @junrushao1994 @tqchen @Lunderberg can you look at this one
again?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/71#issuecomment-1184767286
You are receiving this because you are subscribed to this thread.
Message ID:
@driazati could you give a bit more context here? is there a bug describing
what's wrong right now?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11938#issuecomment-1182050322
You are receiving this because you are subscribed to this thread.
Message ID
@tqchen just to clarify, do we then add this to the DLPack repo or do we
consider this a specialized use of lane internal to TVM?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/18#issuecomment-1182206471
You are receiving this because you are subscr
i have no concerns here, @manupa-arm feel free to submit this when you're ready
to start
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/81#issuecomment-1182188871
You are receiving this because you are subscribed to this thread.
Message ID:
i've put this RFC on the meeting agenda for this week's Community Meeting
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/84#issuecomment-1180909624
You are receiving this because you are subscribed to this thread.
Message ID:
@tqchen i think one goal we should have with this RFC is to codify things like
> When a function does not have global_symbol attribute, it means the
> LinkageType is private
the purpose is not to codify it so that we can't change it, but just so that we
are all on the same page here. perhaps we
we should try and fix https://github.com/apache/tvm/issues/12022 before we
release as well, i think
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11736#issuecomment-1176512569
You are receiving this because you are subscribed to this thread.
Message
cc @tqchen
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/11989#issuecomment-1172617595
You are receiving this because you are subscribed to this thread.
Message ID:
@manupa-arm i think your summary is roughly correct.
@tqchen @masahi @kparzysz-quic perhaps you guys could have a look and see if we
could resolve the question of how to represent the scalable concept in
DLDataType. also cc @alter-xp in case they would like to leverage this for
RISC-V (i'm awar
cc @mbs-octoml @Mousius @manupa-arm @MichaelJKlaiber @grant-arm @kparzysz-quic
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/84#issuecomment-1171465597
You are receiving this because you are subscribed to this thread.
Message ID:
Hi all,
The next TVM Community Meeting is Wednesday, June 22 at 8:00am PDT, 15:00 UTC,
16:00 BST, 17:00 CEST, 20:30 India, 23:00 China. We are continuing to host this
as a unified meeting with the microTVM Community Meeting.
The agenda for this meeting can be found in the [agenda
doc](https:
@junrushao1994 ok, just want to clarify one question here:
> TVMScript users could write a python/rust code, while it's pretty infeasible
> for them to write JSON with bare hand.
what functionality does JSON provide that TVMScript doesn't do right now as
it's designed? Is there a reason to have
thanks @alter-xp, the PR is now merged! please open an RFC tracking issue and
list out the PRs we can expect there, then we can proceed on the CI changes.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/75#issuecomment-1156983012
You are receiving th
Merged #75 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/75#event-6816322214
You are receiving this because you are subscribed to this thread.
Message ID:
Hi all,
I don't see an agenda topic for this week, so let's cancel this meeting.
Andrew
---
[Visit
Topic](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-june-15-2022-cancelled/12950/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe
@junrushao1994 ah thanks for clarifying! a few follow-ups then:
> Imagine you are a rust user who doesn't want to use python, our proposal
> makes it possible to develop a frontend in pure rust. And of course, it's not
> going to be our priority, i'm just stating the possibility.
Does this mean
thanks for summarizing @junrushao1994 . to provide some additional perspective:
- I'd really like us to get to a place where we have 1 reliable and readable
format to serialize TIR. i don't think we should build all of this
infrastructure just to provide a "best-effort" serialization--anything
e
@alter-xp we have some:
- about the CI environment:
https://tvm.apache.org/docs/contribute/pull_request.html#ci-environment
- about building docker containers locally:
https://github.com/apache/tvm/blob/main/docker/README.md
we need to write that up :/
the basics are:
1. submit a PR which only
cc @kparzysz-quic @tqchen @jwfromm @masahi @junrushao1994 @comaniac
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/78#issuecomment-1152677669
You are receiving this because you are subscribed to this thread.
Message ID:
Hi all,
The next TVM Community Meeting is Wednesday, June 15 at 8:00am PDT, 15:00 UTC,
16:00 BST, 17:00 CEST, 20:30 India, 23:00 China. We are continuing to host this
as a unified meeting with the microTVM Community Meeting.
The agenda for this meeting can be found in the [agenda
doc](https:
Merged #70 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/70#event-6781982914
You are receiving this because you are subscribed to this thread.
Message ID:
> people use text format for readability, and in most usecases, go for json
> reliable serialization.
what do you mean by "reliable" here? if they're truly roundtrippable, aren't
they both reliable? just trying to understand :)
> Instead, for metaprogramming capability, one may need to interlea
[quote="mbs-octoml, post:6, topic:12944"]
Other than the plumbing, is there an issue with threading a name supply so that
globals have a unique and appropriately hinted name at birth?
[/quote]
One question in my mind is: there are some names which must be stable e.g.
`__main__`, `get_c_metadat
we discussed this at the June 6 [community
meeting](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-june-8-2022/12900).
a significant chunk of the meeting was spent presenting the RFC, and we had
about 15 minutes of discussion at the end.
i think there is more to be discussed here.
The recording has been [posted](https://youtu.be/1fSfhgVp0ms).
---
[Visit
Topic](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-june-8-2022/12900/3)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](http
i agree with that direction, but I think to do that requires us to merge the
IRModules so that mangling transforms are applied globally rather than to just
a part of the program. do you agree?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/pre-rfc-name-mangling-in-irmodules/12944/5)
One related thing was that we intended to consolidate all of the different
functions into one IRModule (e.g. those passed to external codegen with those
passed to ordinary TVM codegen). If we had done that, we could probably do the
following:
- If a Relay-to-Runtime hook is used, find a way t
Hi all,
In [[mini-RFC] Name mangling in
AOT](https://discuss.tvm.apache.org/t/mini-rfc-name-mangling-in-aot/9907), we
discussed ways to accommodate the `runtime::Module` tree in an embedded
environment, where we prefer to call functions directly in the generated C
using their symbol name rat
very sorry for the delay here.
@junrushao1994 i guess i'm still a little fuzzy on the rationale for why we
want to have two ways to parse TVMScript. I know this is a bit bigger than just
this RFC, but with this RFC we're further pushing the cart down this path so
I'd like us to be explicit abou
Please join us in welcoming @tkonolige as a new committer to TVM! Tristan has
been consistently contributing to all parts of TVM, from the runtimes to the
frontends, schedulers, tuning, documentation, CI and general bug fixing.
Notably, he contributed libbacktrace and PAPI support.
- [Commits
Looks like we've got [Buffer Layout Padding
RFC](https://github.com/apache/tvm-rfcs/pull/77) on the agenda tomorrow. Hope
to see you there!
---
[Visit
Topic](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-june-8-2022/12900/2)
to respond.
You are receiving this because you e
this is on the agenda for tomorrow's [community
meeting](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-june-8-2022/12900).
Perhaps we could discuss in higher bandwidth there?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/77#issuecomm
thanks @MichaelJKlaiber @PaulPalomeroBernardo @cgerum and others! the RFC is
now merged. Please open a tracking issue and link it from this thread for
discoverability.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/60#issuecomment-1143757298
You ar
Merged #60 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/60#event-6720215338
You are receiving this because you are subscribed to this thread.
Message ID:
cc @Mousius @manupa-arm @leandron
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/76#issuecomment-1142686653
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #67 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/67#event-6710896579
You are receiving this because you are subscribed to this thread.
Message ID:
Thanks all for the comments, the vote has passed and we'll merge this RFC.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/67#issuecomment-1142312909
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #11415 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11415#event-6710889810
You are receiving this because you are subscribed to this thread.
Message ID:
+1
The voting period has concluded with the following results:
+1 (6 binding*):
Leandro*
Tianqi*
Andrew Luo
Cody*
Masa*
Jared*
Chris Sullivan
Josh Fromm
Luke Hutton
Xiyou
Andrew*
0: none
-1: none
The vote has passed and the RFC is accepted.
--
Reply to this email directly or view it on Git
1 - 100 of 307 matches
Mail list logo
