Dear SuiteCRM Community members:
As you may be aware that the scheduled end-of-life (EOL) of the 7.8.x LTS version is fast approaching, we’d like to open up this thread for discussion on the challenges you currently have with upgrading away from 7.8 as well as the opportunities, so you can stay up to date with new features, new bugfixes and security fixes.
We know that initially the transition from 7.8 to 7.9 wasn’t smooth for everybody, and in fact many of you opted to stick with the older version, mostly due to the new Theme and the Email module. Are there other aspects that the soon-to-be unsupported LTS provides that you would miss when upgraded to the latest LTS (7.10.x), or to 7.11.x?
While there is always ongoing work on bug fixes and areas to improve in 7.10.x, we have had the chance to answer some of the concerns about the theme (better contrast, smaller spacing, some colour options), and to enhance the latest versions in terms of technology: Bootstrap UI, automated tests, better dependency handling with Composer, new API, re-factoring of some parts of the code, cool new features.
So, we’d like to hear your feedback on how we can help you transcend to the latest versions. We aim to assist as many people as possible whilst being realistic on what we can achieve before 7.8.x end-of-life is reached. Although our product team is working in parallel on SuiteCRM 8 with our normal releases we felt that this focus on LTS end-of-life is extremely crucial to us and the community so I’m sure if we work together, as a team, we can achieve a happy SuiteCRM 7.10.x LTS transition for the majority of users.
I’d like to be able to think of this year that the SuiteCRM product team will grow and expand with the combined members from both the SalesAgility team and the dedicated community members. Together we can develop and contribute efficiently and seamlessly to take in those contributions.
So we’d like to hear from you and come together …
What specific concerns do you have about upgrading away from 7.8.x? What’s keeping you from upgrading?
Do you need help setting up test labs to rehearse the upgrade or test the new version?
Are all your Issues properly reported on GitHub, properly labelled, with enough information to be useful? Is the current method of identifying critical issues not effective enough? Maybe you can add a comment or an up vote there explaining why this is critical for your upgrade.
If you tried, say, v 7.9.4 and gave up on that branch, can you try something newer now?
Can you help with any of the stuff that is missing before you can upgrade like help test bug fixes or provide screen cast of your issues? Let’s coordinate this work!