Hi,
Here is the proposed release schedule for the next 2 releases:
12.0.1
May 11: 12.0.1-rc1
June 8: 12.0.1-rc2
June 22: 12.0.1-final
13.0.0
July 27: release/13.x branch created
July 30: 13.0.0-rc1
Aug 24: 13.0.0-rc2
Sep 7: 13.0.0-rc3
Sep 21: 13.0.0-final
If there are no objections, I w
In my view, this email is really too different topics. Given that, my
response is split into two parts.
First, should we make phabricator our default for code review? I am not
opposed to this. I don't particular support it either, but I would not
spend time arguing against it. I would sugg
I'll defer to Christian the discussion about this section.
+Christian
--
Krzysztof Parzyszek kparz...@quicinc.com AI tools development
-Original Message-
From: cfe-dev On Behalf Of Kevin P. Neal via
cfe-dev
Sent: Monday, May 3, 2021 1:57 PM
To: Krzysztof Parzyszek via llvm-dev
Cc:
On Mon, 3 May 2021, Krzysztof Parzyszek via cfe-dev wrote:
Potential future direction:
This section presents a potential future evolution of the review process.
Christian has conducted experiments suggesting that we can replace the
XXX-commits mailing lists with notifications directly from Pha
Statement:
Our current code review policy states[1]:
"Code reviews are conducted, in order of preference, on our web-based
code-review tool (see Code Reviews with Phabricator), by email on the relevant
project's commit mailing list, on the project's development list, or on the bug
tracker."
