Skip to content

Remove "master" References #14742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 28, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions contributing/documentation/overview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ branch of the ``upstream`` remote, which is the original Symfony Docs repository
Fixes should always be based on the **oldest maintained branch** which contains
the error. Nowadays this is the ``4.4`` branch. If you are instead documenting a
new feature, switch to the first Symfony version that included it, e.g.
``upstream/3.1``. Not sure? That's OK! Just use the ``upstream/master`` branch.
``upstream/3.1``.

**Step 5.** Now make your changes in the documentation. Add, tweak, reword and
even remove any content and do your best to comply with the
Expand Down Expand Up @@ -295,12 +295,12 @@ Please be patient. It can take up to several days before your pull request can
be fully reviewed. After merging the changes, it could take again several hours
before your changes appear on the Symfony website.

Why Should I Use the Oldest Maintained Branch Instead of the Master Branch?
Why Should I Use the Oldest Maintained Branch Instead of the Latest Branch?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Consistent with Symfony's source code, the documentation repository is split
into multiple branches, corresponding to the different versions of Symfony itself.
The ``master`` branch holds the documentation for the development branch of
The latest (e.g. ``5.x``) branch holds the documentation for the development branch of
the code.

Unless you're documenting a feature that was introduced after Symfony 4.4,
Expand Down