[wp-trac] [WordPress Trac] #57883: block_core_comment_template_render_comments() fatal error
WordPress Trac
noreply at wordpress.org
Tue Mar 14 16:47:40 UTC 2023
#57883: block_core_comment_template_render_comments() fatal error
-------------------------------------------------+-------------------------
Reporter: gqevu6bsiz | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 6.2.1
Component: Comments | Version: 6.1
Severity: normal | Resolution:
Keywords: has-patch gutenberg-merge has- | Focuses:
screenshots needs-testing needs-unit-tests |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):
* keywords: has-patch gutenberg-merge has-screenshots =>
has-patch gutenberg-merge has-screenshots needs-testing needs-unit-
tests
* milestone: 6.2 => 6.2.1
Comment:
After discussing with Core Committers in Make/Core slack,
[https://wordpress.slack.com/archives/C02RQBWTW/p1678809472616959 there's
consensus for the following]:
* Punt this fix to 6.2.1
* Add tests in Gutenberg and Core for this fix
And for the question of if a fatal error from a previous release can be
considered during a current RC cycle:
>When in a RC cycle, fatal errors from a previous release can be
considered on a case-by-case basis with open committer discussions (like
the one started here today). BUT serious consideration should be given to
whether that fatal error fix should go into the RC including minimum
criteria of must-have automated tests and the risk assessments of the code
changes.
Punting this ticket to 6.2.1.
Its fix will be part of a `@wordpress` packages update commit as the file
in question is maintained in Gutenberg and not in Core.
Though reported upstream, keeping this ticket open due to the fatal error
for tracking and awareness.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/57883#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list