[#28366] - Deprecating "new" MVC for 4.0 instead of 5.0
- Fixed in Code Base
- 2 Apr 2020
- Medium
- Build: staging
- # 28366
- Diff
- Hackwar:j3deprecateMVC
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success continuous-integration/appveyor/pr AppVeyor build succeeded Details
- Success continuous-integration/drone/pr Build is passing Details
- Pending Hound Hound is busy sniffing around... Details
User tests: Successful: Unsuccessful:
This is an accompanying PR to #28365. The aim is to deprecate the "new" MVC classes for 4.0 instead of 5.0.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Libraries |
| Labels |
Added:
?
|
||
Surely it is too late for this. The version that will contain the deprecation notice is released on the same day
@brianteeman That would be true if he wanted to add the deprecation notice to 3.10. But he wants to add it to staging.
Just merge this and the companion pull request and be done with it already. For the record, 3.9 has been full of semantic versioning violations so what's another one at this point, clearly the project only cares about following its development strategy when it is convenient for the project to do so.
I formally rescind all arguments against this change if it means people will pledge to focus on the other 2349078 tasks that have kept 4.0 in development hell for 5 years now.
Given the creation of https://github.com/joomla-extensions/legacy-mvc (yay for more abandonware "core supported" extensions), this should be merged so developers might notice this deprecation now and not get bitten by the sudden removal in 4.0.
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-04-02 06:24:29 |
| Closed_By | ⇒ | HLeithner |
Thanks
Surely it is too late for this. The version that will contain the deprecation notice is released on the same day