Moving Frappe CRM, Helpdesk & Learning to v15 and v16 specific versions

For the longest time business apps i.e. CRM, Helpdesk and Learning have carried a single separate version. This created a lot of confusion between the feature parity and comparison with framework version 15 and version 16 respectively. Also it was getting harder for maintainers to keep up with multiple version in single branch, especially with the updates that have been pushed in the framework v16 as of late.

Hence the reasonable thing to do was to maintain to separate versions. As of now we have created 2 branches in each app’s individual repo which is similar to the structure that framework and rest of the major frappe applications follow i.e. version-15 and version-16. Obviously this means that there will be 2 version of each application v16.x.x and v15.x.x corresponding to framework versions of v16 and v15.

All the new updates and feature will go to v16 moving forward and v15 will get bug fixes only as it is going to reach EOL soon. No existing sites on frappe cloud will be impacted by this and we will make sure that you are migrated to your respective version and get updates from that only moving forward so that there is no confusion. This also sets up cadence moving forward and removes confusion around the availability of features that utilize the framework features that only exist in v16.

This is a welcome improvement, especially for those evaluating Frappe for long-term business use.

Separating the versions should make compatibility and maintenance much clearer.

One thing I’d be interested in seeing is more guidance around migrating custom applications and integrations from v15 to v16, particularly how to identify breaking changes before upgrading production environments.

Are there plans for a centralized compatibility checklist or migration report for business apps?

Can the same be done for Insights and Lending as those are the only two remaining Frappe Apps which this same confusion exists on Supported versions - Frappe.

@ps173 that is great news!

would it be possible to add “tagging” to GitHub - frappe/payments: A payments app for frappe · GitHub as well then?

I’ve been requesting this for at least a year and a half. It’s great to see that you finally took the plunge!

There are migration guides in the GitHub Wiki for Frappe Framework and ERPNext. Unfortunately, the ERPNext team does not maintain them at the moment. Framework is a bit better.