What are the intermediary steps for someone who has created or maintains a module to prepare it for compatibility with upcoming releases of the core? A module doesn't work without the core, and the core alone isn't enough to create a website. We need them to progress in parallel.
With the changes in the later releases of 1.4, and the removal of deprecated functions, files, and folders in 1.5, the original scope for 2.0 has been realized, at least based on this (and others) - Navigating ahead - ImpressCMS Compass 2012. Maybe we should relabel 1.5 as 2.0 and what is in 2.0 as 3.0.
Is the information in the debug panel enough to help get a module ready for what's next?
This Post was from: https://www.impresscms.org/iforum/viewtopic.php?topic_id=5924&post_id=50794