Timeline for How long does a deprecated function live in core?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2012 at 2:50 | vote | accept | Brian Fegter | ||
| Mar 1, 2012 at 1:40 | answer | added | Otto | timeline score: 12 | |
| Feb 29, 2012 at 22:32 | comment | added | SickHippie | @BrianFegter - sure thing! | |
| Feb 29, 2012 at 22:31 | answer | added | SickHippie | timeline score: 2 | |
| Feb 29, 2012 at 21:41 | answer | added | Dougal Campbell | timeline score: 3 | |
| Feb 29, 2012 at 21:35 | comment | added | Brian Fegter | @SickHippie Can you please make your comment an answer? | |
| Feb 29, 2012 at 20:53 | comment | added | SickHippie | There was some discussion a couple years ago to have a set number of releases between deprecation and removal, but at the time deprecation was poorly handled. There were a number of functions that did not have an @deprecated version number filled in, certain functions were widely used by loosely maintained plugins, and so on. It doesn't seem like there was any real resolution to the matter either. | |
| Feb 29, 2012 at 20:49 | history | tweeted | twitter.com/#!/StackWordPress/status/174959522484465664 | ||
| Feb 29, 2012 at 18:28 | comment | added | kaiser | WordPress clearly states that it isn't backwards compatible (or, at least, doesn't care about it). The only reason I can imagine, is that they don't want to break all those outdated plugins. | |
| Feb 29, 2012 at 18:26 | answer | added | kaiser | timeline score: 6 | |
| Feb 29, 2012 at 16:00 | history | asked | Brian Fegter | CC BY-SA 3.0 |