Skip to content

Commit 8ea278a

Browse files
authored
Merge pull request #25 from Ivorforce/review-timeline
Add a short section about when pull requests are reviewed.
2 parents 461af99 + c34813f commit 8ea278a

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

organization/pull_requests/review_process.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,3 +52,21 @@ Even if you are not a maintainer, you can still help by reviewing code,
5252
providing feedback on PRs and testing PRs locally on your machine to confirm
5353
that they work as intended. Many of the currently active maintainers started out
5454
doing this before they became maintainers.
55+
56+
When will a pull request get reviewed?
57+
--------------------------------------
58+
59+
When you open a new pull request, :ref:`Area maintainers <doc_areas>` are notified immediately.
60+
61+
However, a lot of pull requests are opened every day, so reviews can take a while to come in. Going by historical data,
62+
you can expect the following review timelines:
63+
64+
- 80% of **regression fixes** are merged (or rejected) within **a week**.
65+
- 80% of **bug fixes** are merged (or rejected) within **two weeks**.
66+
- 80% of **enhancements** are merged (or rejected) within **two months**.
67+
68+
As you can imagine, simple pull requests will usually be reviewed more quickly than large and complicated pull requests.
69+
70+
If you think your pull request has been overlooked, feel free to ask about it in the `Contributors' chat <https://chat.godotengine.org>`__.
71+
You can ask in `#new-contributors <https://chat.godotengine.org/channel/new-contributors>`__, `#devel <https://chat.godotengine.org/channel/devel>`__,
72+
or the channel of the :ref:`area <doc_areas>` you're expecting reviews from.

0 commit comments

Comments
 (0)