<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm-project.git/llvm/docs/CodeReview.rst, branch users/nico/python-2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/'/>
<entry>
<title>[llvm][docs] Add notes on upstreaming code from downstream projects (#129743)</title>
<updated>2025-03-12T11:17:19+00:00</updated>
<author>
<name>Andrzej Warzyński</name>
<email>andrzej.warzynski@arm.com</email>
</author>
<published>2025-03-12T11:17:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=77b55c76acebf30d3951788d1651607d5276380e'/>
<id>77b55c76acebf30d3951788d1651607d5276380e</id>
<content type='text'>
For context, see:
* https://discourse.llvm.org/t/code-review-process-when-upstreaming-patches</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
For context, see:
* https://discourse.llvm.org/t/code-review-process-when-upstreaming-patches</pre>
</div>
</content>
</entry>
<entry>
<title>[docs] Update docs on code-review process (#111735)</title>
<updated>2024-11-06T07:39:43+00:00</updated>
<author>
<name>Andrzej Warzyński</name>
<email>andrzej.warzynski@arm.com</email>
</author>
<published>2024-11-06T07:39:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=41248b598b8b18febc62ea61938870def2421126'/>
<id>41248b598b8b18febc62ea61938870def2421126</id>
<content type='text'>
Clarify expectations for handling new comments post-LGTM but pre-commit.

This change aims to standardize expectations when new comments are added
after a patch has received LGTM but before it has been committed.
Currently, approaches to this vary, and this update seeks to clarify
best practices.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Clarify expectations for handling new comments post-LGTM but pre-commit.

This change aims to standardize expectations when new comments are added
after a patch has received LGTM but before it has been committed.
Currently, approaches to this vary, and this update seeks to clarify
best practices.</pre>
</div>
</content>
</entry>
<entry>
<title>[llvm][docs] Add Approvals section to GitHub guide (#113434)</title>
<updated>2024-10-31T15:24:33+00:00</updated>
<author>
<name>David Spickett</name>
<email>david.spickett@linaro.org</email>
</author>
<published>2024-10-31T15:24:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=a1c6dc223ee1eedc049890676992b508ebd6b623'/>
<id>a1c6dc223ee1eedc049890676992b508ebd6b623</id>
<content type='text'>
Based on feedback that when reading the document as a guide, it's odd
that it skips right from updating the PR to merging it.

The section is a link to the existing Code Review guide's text on the
topic.

I have updated that to mention required reviewers, which some
subprojects do use (libcxx is one) but most don't.

Also we use the words "accepted" and "approved" interchangeably, so I've
swapped one instance so it's consistent between paragraphs.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Based on feedback that when reading the document as a guide, it's odd
that it skips right from updating the PR to merging it.

The section is a link to the existing Code Review guide's text on the
topic.

I have updated that to mention required reviewers, which some
subprojects do use (libcxx is one) but most don't.

Also we use the words "accepted" and "approved" interchangeably, so I've
swapped one instance so it's consistent between paragraphs.</pre>
</div>
</content>
</entry>
<entry>
<title>Replace documentation mentions of IRC with Discord (#114276)</title>
<updated>2024-10-31T13:22:46+00:00</updated>
<author>
<name>Aaron Ballman</name>
<email>aaron@aaronballman.com</email>
</author>
<published>2024-10-31T13:22:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=0ab44fd2464354dfdca0e7afacbb21a84bca46d9'/>
<id>0ab44fd2464354dfdca0e7afacbb21a84bca46d9</id>
<content type='text'>
This does not touch code owners or credits files that list IRC handles,
that can be done separately if we want to make that change.

See
https://discourse.llvm.org/t/rfc-remove-irc-as-a-recommended-communication-channel/82808/3
for the RFC.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This does not touch code owners or credits files that list IRC handles,
that can be done separately if we want to make that change.

See
https://discourse.llvm.org/t/rfc-remove-irc-as-a-recommended-communication-channel/82808/3
for the RFC.</pre>
</div>
</content>
</entry>
<entry>
<title>[docs] Point to Discourse for creating RFCs (#114341)</title>
<updated>2024-10-31T12:35:57+00:00</updated>
<author>
<name>Jan Svoboda</name>
<email>jan_svoboda@apple.com</email>
</author>
<published>2024-10-31T12:35:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=3f17613509167e9e0e1502b162524b7f484b39aa'/>
<id>3f17613509167e9e0e1502b162524b7f484b39aa</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[Policy] Replace "code owners" with "maintainers" (#107384)</title>
<updated>2024-09-16T17:05:03+00:00</updated>
<author>
<name>Aaron Ballman</name>
<email>aaron@aaronballman.com</email>
</author>
<published>2024-09-16T17:05:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=c0719d8c08f440feab09418f02e5937426756b40'/>
<id>c0719d8c08f440feab09418f02e5937426756b40</id>
<content type='text'>
This replaces the previous Code Owners section of our developer policy
with a new section for Maintainers. It also updates most of the places
we mention "code owner" in the documentation (it does not update the
files named `Code Owners.rst` or similar because those should be updated
when the subprojects add their `Maintainers.rst` file).

The wording was taken from what was proposed in the RFC (including all
suggested amendments from folks on the thread).

Please see the RFC for more details:

https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714/</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This replaces the previous Code Owners section of our developer policy
with a new section for Maintainers. It also updates most of the places
we mention "code owner" in the documentation (it does not update the
files named `Code Owners.rst` or similar because those should be updated
when the subprojects add their `Maintainers.rst` file).

The wording was taken from what was proposed in the RFC (including all
suggested amendments from folks on the thread).

Please see the RFC for more details:

https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714/</pre>
</div>
</content>
</entry>
<entry>
<title>[docs] Add note about "Re-request review" (#104735)</title>
<updated>2024-08-19T16:53:03+00:00</updated>
<author>
<name>Vitaly Buka</name>
<email>vitalybuka@google.com</email>
</author>
<published>2024-08-19T16:53:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=93d0f82272dc230ff4d53d48c43b2f1518754a7b'/>
<id>93d0f82272dc230ff4d53d48c43b2f1518754a7b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>llvm/docs: Try to fix some broken links</title>
<updated>2024-03-09T02:19:32+00:00</updated>
<author>
<name>David Blaikie</name>
<email>dblaikie@gmail.com</email>
</author>
<published>2024-03-09T02:19:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=2709bafbfe54b75003c60a950605194d6a3c9776'/>
<id>2709bafbfe54b75003c60a950605194d6a3c9776</id>
<content type='text'>
I messed up the syntax here previously - let's see if this is enough to
get it working.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I messed up the syntax here previously - let's see if this is enough to
get it working.
</pre>
</div>
</content>
</entry>
<entry>
<title>Document use of `skip-precommit-approval` label for non-review pull requests (#81053)</title>
<updated>2024-02-09T00:41:04+00:00</updated>
<author>
<name>David Blaikie</name>
<email>dblaikie@gmail.com</email>
</author>
<published>2024-02-09T00:41:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=93471466be65cf78330782d461a821ffb82e070a'/>
<id>93471466be65cf78330782d461a821ffb82e070a</id>
<content type='text'>
Derived from this discussion:
https://discourse.llvm.org/t/prs-without-approvals-muddy-the-waters/76656</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Derived from this discussion:
https://discourse.llvm.org/t/prs-without-approvals-muddy-the-waters/76656</pre>
</div>
</content>
</entry>
<entry>
<title>[llvm][Docs] Update MyFirstTypoFix doc (#79149)</title>
<updated>2024-01-29T10:34:22+00:00</updated>
<author>
<name>David Spickett</name>
<email>david.spickett@linaro.org</email>
</author>
<published>2024-01-29T10:34:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=ba5d92eb9c18a9037dd06a74f90ceba3f4e3ace9'/>
<id>ba5d92eb9c18a9037dd06a74f90ceba3f4e3ace9</id>
<content type='text'>
I've not tried to change the purpose or style of the doc, just edited
for clarity and removed any Phabricator related language in favour of
GitHub terms.

Where possible, I've swapped direct links to LLVM's website with RST
links to the local documents. Which should be a bit more resilient.

Also it's less confusing if you're editing multiple pages locally, you
don't accidentally end up on the live site.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I've not tried to change the purpose or style of the doc, just edited
for clarity and removed any Phabricator related language in favour of
GitHub terms.

Where possible, I've swapped direct links to LLVM's website with RST
links to the local documents. Which should be a bit more resilient.

Also it's less confusing if you're editing multiple pages locally, you
don't accidentally end up on the live site.</pre>
</div>
</content>
</entry>
</feed>
