File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed
Filter options
Expand file tree Collapse file tree 1 file changed +4
-4
lines changed
Original file line number Diff line number Diff line change 1
1
| Q | A
2
2
| ------------- | ---
3
- | Branch? | 5.4 for features / 4.4 or 5.3 for bug fixes <!-- see below -->
3
+ | Branch? | 6.1 for features / 4.4, 5.3, 5.4 or 6.0 for bug fixes <!-- see below -->
4
4
| Bug fix? | yes/no
5
5
| New feature? | yes/no <!-- please update src/**/CHANGELOG.md files -->
6
6
| Deprecations? | yes/no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
7
7
| Tickets | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
8
8
| License | MIT
9
9
| Doc PR | symfony/symfony-docs#... <!-- required for new features -->
10
10
<!--
11
- Replace this notice by a short README for your feature/bugfix. This will help people
12
- understand your PR and can be used as a start for the documentation.
11
+ Replace this notice by a short README for your feature/bugfix.
12
+ This will help reviewers and should be a good start for the documentation.
13
13
14
14
Additionally (see https://symfony.com/releases):
15
15
- Always add tests and ensure they pass.
16
- - Never break backward compatibility (see https://symfony.com/bc).
17
16
- Bug fixes must be submitted against the lowest maintained branch where they apply
18
17
(lowest branches are regularly merged to upper ones so they get the fixes too.)
19
18
- Features and deprecations must be submitted against branch 5.x.
20
19
- Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
20
+ - Never break backward compatibility (see https://symfony.com/bc).
21
21
-->
You can’t perform that action at this time.
0 commit comments