[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 dd32):

 > Thoughts?

 There is no huge "Backwards incompatible change" here, There is a bug,
 which has affected the last half a dozen releases which is fixed for 3.2
 onwards, those upgrading who skip the 3.1-3.2 step might will trigger it
 again, however, it's not a harmful bug, it's one that people have lived
 with over time (akismet getting re-installed upon upgrade). Even then,
 That might be nulled by a API change that's in the works.

 to make it clear: Those upgrading from 2.9 to 3.3 will be able to do it,
 this change will not prevent that, They will however, get akismet re-
 installed if they've removed it.

 furthermore, That version numbering is not the version numbering WordPress
 utilises. (x.y) is the major version, (x.y.z) is the "patch" version(We
 don't have a "minor" release, the latter is generally called a minor
 release, or a point release), 2.8->2.9 holds the same weight as 2.9->3.0,
 which will be the same as 3.9->4.0.

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