Skip to content

Commit 598b6a5

Browse files
committed
Merge branch '4.2' into 4.3
* 4.2: Don't mention the Symfony Standard edition in the contributing docs
2 parents f9f806d + 1646cb6 commit 598b6a5

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

contributing/community/reviews.rst

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -58,16 +58,16 @@ The steps for the review are:
5858

5959
#. **Is the Report Complete?**
6060

61-
Good bug reports contain a link to a fork of the `Symfony Standard Edition`_
62-
(the "reproduction project") that reproduces the bug. If it doesn't, the
63-
report should at least contain enough information and code samples to
64-
reproduce the bug.
61+
Good bug reports contain a link to a project (the "reproduction project")
62+
created with the `Symfony skeleton`_ or the `Symfony website skeleton`_
63+
that reproduces the bug. If it doesn't, the report should at least contain
64+
enough information and code samples to reproduce the bug.
6565

6666
#. **Reproduce the Bug**
6767

6868
Download the reproduction project and test whether the bug can be reproduced
6969
on your system. If the reporter did not provide a reproduction project,
70-
create one by forking_ the `Symfony Standard Edition`_.
70+
create one based on one `Symfony skeleton`_ (or the `Symfony website skeleton`_).
7171

7272
#. **Update the Issue Status**
7373

@@ -96,7 +96,7 @@ The steps for the review are:
9696
9797
Thank you @weaverryan for creating this bug report! This indeed looks
9898
like a bug. I reproduced the bug in the "kernel-bug" branch of
99-
https://github.com/webmozart/symfony-standard.
99+
https://github.com/webmozart/some-project.
100100
101101
Status: Reviewed
102102
@@ -134,9 +134,9 @@ Pick a pull request from the `PRs in need of review`_ and follow these steps:
134134
#. **Reproduce the Problem**
135135

136136
Read the issue that the pull request is supposed to fix. Reproduce the
137-
problem on a clean `Symfony Standard Edition`_ project and try to understand
138-
why it exists. If the linked issue already contains such a project, install
139-
it and run it on your system.
137+
problem on a new project created with the `Symfony skeleton`_ (or the
138+
`Symfony website skeleton`_) and try to understand why it exists. If the
139+
linked issue already contains such a project, install it and run it on your system.
140140

141141
#. **Review the Code**
142142

@@ -211,7 +211,8 @@ Pick a pull request from the `PRs in need of review`_ and follow these steps:
211211
212212
.. _GitHub: https://github.com
213213
.. _Symfony issue tracker: https://github.com/symfony/symfony/issues
214-
.. _Symfony Standard Edition: https://github.com/symfony/symfony-standard
214+
.. _`Symfony skeleton`: https://github.com/symfony/skeleton
215+
.. _`Symfony website skeleton`: https://github.com/symfony/website-skeleton
215216
.. _create a GitHub account: https://help.github.com/articles/signing-up-for-a-new-github-account/
216217
.. _forking: https://help.github.com/articles/fork-a-repo/
217218
.. _bug reports in need of review: https://github.com/symfony/symfony/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22Bug%22+label%3A%22Status%3A+Needs+Review%22+

0 commit comments

Comments
 (0)