In this case, were assembling a whole new car next to the one were in, driving both, and still at 75/mph. In the past weve often talked about upgrading websites feeling like working on cars engine, while driving down the highway at 75/mph. Were going to make some changes to our marketplace here to support 5.7 add-ons/themes as well as 5.6 ones too. Weve made a commitment to continue supporting 5.6.x for security and critical bugs for at least a year. This does throw our typical release approach somewhat on its head, however. Wordpress NEVER does this, Drupal ALWAYS does this - were right in the middle: once every half a decade or so seems reasonable. We know that when you start playing with 5.7 youll see why we made this hard choice, but we want you to also know were not going to abandon upgrades again lightly. Theres so much good new stuff in concrete5.7 that weve been able to include because we simply decided folks would have to migrate by hand instead of upgrading with a single click. The ecosystem of 3rd party tools and PHP itself has changed quite a bit in the last half a decade, and we dont want to be stuck in the past. We really wanted to have a clean slate, so we could embrace ideas that involved deep changes to the system. Its always been important to us to keep everyone moving forward together.įor the first time in 6 years, weve decided to not put backward compatibility first and foremost. You can take a 5.0 website and hit Update all the way through 5.6.3.1. In that time weve had 40+ version releases, 6 major ones, and weve always maintained backward compatibility.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |