[wp-trac] [WordPress Trac] #57586: term_exists() return type not consistent regarding wp_insert_term()

[WordPress Trac]

#57586: term_exists() return type not consistent regarding wp_insert_term()
-------------------------------------------------+-------------------------
 Reporter:  hugod                                |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.4
Component:  Taxonomy                             |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback early needs-  |     Focuses:
  dev-note                                       |
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 I'm doing an audit of all 6.4 `early` tickets to determine if each should
 or shouldn't be in the `early` queue.

 [https://make.wordpress.org/core/handbook/contribute/trac/keywords/ The
 handbook explains the `early` keyword as]:
 >This keyword should only be applied by committers. The keyword signals
 that the ticket is a priority, and should be handled early in the next
 release cycle.

 `early` means the commits need to happen during the early part of the
 Alpha cycle; else, the ticket gets bumped out of the current milestone.

 Is this ticket an `early` candidate?

 Yes. Why? There are mentions of a potential BC (backward compatible)
 break. If yes, then careful consideration is needed and commit(s) should
 be done as early as possible to give a longer period of time for extender
 awareness, feedback, and testing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57586#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform