File tree 1 file changed +4
-5
lines changed
Filter options
1 file changed +4
-5
lines changed
Original file line number Diff line number Diff line change 3
3
| Branch? | 4.4 for features / 3.4 or 4.3 for bug fixes <!-- see below -->
4
4
| Bug fix? | yes/no
5
5
| New feature? | yes/no <!-- please update src/**/CHANGELOG.md files -->
6
- | BC breaks? | no <!-- see https://symfony.com/bc -->
7
6
| Deprecations? | yes/no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
8
- | Tests pass? | yes <!-- please add some, will be required by reviewers -->
9
- | Fixed tickets | #... <!-- #-prefixed issue number(s), if any -->
7
+ | Tickets | Fix #... <!-- prefix each issue number with "Fix #", if any -->
10
8
| License | MIT
11
9
| Doc PR | symfony/symfony-docs#... <!-- required for new features -->
12
-
13
10
<!--
14
11
Replace this notice by a short README for your feature/bugfix. This will help people
15
12
understand your PR and can be used as a start for the documentation.
16
13
17
14
Additionally (see https://symfony.com/roadmap):
15
+ - Always add tests and ensure they pass.
16
+ - Never break backward compatibility (see https://symfony.com/bc).
18
17
- Bug fixes must be submitted against the lowest maintained branch where they apply
19
- (lowest branches are regularly merged to upper ones so they get the fixes too).
18
+ (lowest branches are regularly merged to upper ones so they get the fixes too.)
20
19
- Features and deprecations must be submitted against branch 4.4.
21
20
- Legacy code removals go to the master branch.
22
21
-->
You can’t perform that action at this time.
0 commit comments