[wp-trac] [WordPress Trac] #17173: Review the usage of _copy_dir() introduced in #14484

[WordPress Trac]

#17173: Review the usage of _copy_dir() introduced in #14484
-----------------------------+-----------------------
 Reporter:  dd32             |       Owner:  dd32
     Type:  defect (bug)     |      Status:  accepted
 Priority:  normal           |   Milestone:  3.2
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  3.3-early        |
-----------------------------+-----------------------

Comment (by westi):

 Replying to [comment:5 sterlo]:
 > Introducing code that would keep people using < 3.2 from upgrading to
 3.3 could cause some serious issues.
 >
 > "Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards
 compatible functionality is introduced to the public API. It MAY be
 incremented if substantial new functionality or improvements are
 introduced within the private code. It MAY include patch level changes."
 >
 > "Major version X (X.y.z | X > 0) MUST be incremented if any backwards
 incompatible changes are introduced to the public API. It MAY include
 minor and patch level changes."
 >
 > http://semver.org/
 >
 > Thoughts?

 I'm not sure what this has to do with this ticket at all.

 One of our design goals is backwards compatibility and we don't inflate
 version numbers.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17173#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software