[wp-trac] [WordPress Trac] #47169: Use a non-zero exit code when requirements are not met
WordPress Trac
noreply at wordpress.org
Tue May 7 17:05:33 UTC 2019
#47169: Use a non-zero exit code when requirements are not met
-----------------------------------+---------------------
Reporter: jrf | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.2
Component: Build/Test Tools | Version: 3.0
Severity: normal | Resolution:
Keywords: has-patch 2nd-opinion | Focuses:
-----------------------------------+---------------------
Comment (by jeremyfelt):
Replying to [comment:7 jrf]:
> Of course, one expects devs in the WP sphere to keep up with current
developments, but not everyone does and not all the time.
Very true. Would it be worth publishing a short dev-note on make/core with
a warning?
I don't think there's any issue with things going into trunk today, but
I'm really wary of anything landing in 5.2 on release day beyond the about
page. Even yesterday, a change to `tests/` would feel more comfortable
than today. :)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47169#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list