ERPNext, HRMS & Frappe Framework v16 Release Dates

UI on mobile device

1 Like

I merged a PR today, and the build has just finished :white_check_mark:
v16 is available on Docker Hub :smiley:

6 Likes
1 Like

great news,

is it support press and it’s still run on ubuntu 22.04 only and mariadb 10.6 with edit conifg or improve it

Hi there,when I install finished,we don’t have that dropdown selection about the “Edit Sidebar“.How can I do it?Thank you.

HOW TO BUILD using this image?

Update on the release date. We have decided to delay the stable release considering the following factors:

  • Feedback on beta release + missing polish of new UI changes, especially the new navigation and desktop view.
  • New addition in scope - We are making UI similar to Espresso-based new apps.
  • Ongoing security audit of v16 code changes
  • Pending docs updates
  • Code cleanups, deprecation and migrations

New plan:

  • We’ll continue releasing beta versions as and when major milestones are achieved. Expect 3-4 more beta releases. These can be breaking in nature, so read the accompanying release notes and migration guide before updating.
  • We’ll do a “release candidate” mid-December when we’ve frozen all major changes. Only fixes will be merged after this freeze.
  • Final release will be on 12th January 2026. (~3 weeks after RC release, after intense internal, partner and community-driven testing and fixes)

I know it sucks to wait and delay the release like this, but it’s better to do it right the first time. Let’s (actually) make this the most stable major release so far. :crossed_fingers:

32 Likes

can we atleast, have the crm app, feature parity with erpnext crm, and migrate all current crm from erpnext to the frappe CRM, for v16, it would make alot of sense, to work it out this way, rather than going into v16, with still 2 crm versions, that at some major level dont talk to each other

2 Likes

ERPNext
HRMS
POSAWESOME

Here is download link for ERPNext Production V16 Beta**

ERPNext V16beta ova

Import in Open VirtualBox 7.0 and enjoy. :blush:
Ubuntu Server: **22.04.2 LTS
**

For installation of ERPnext is
username = Administrator
password = admin

For VirtualBox
username = frappe
password = frappe
sql = frappe

@compgeniuses what are the major gaps you see with Frappe CRM that are present in ERPNext CRM? We will plan something like this for maybe v17 though.

I THink Not Algning records in V16, would bee a great wasted Opportunity.

My thought for Implementaiton is, DO not Remove the Current ERPNEXT CRM, retain Both, However, Make it so, Using either of the Apps, either erpnext crm, or Frappe CRM, does not affect Anything at all, and that users, can Add Recrods, in either Side, and Use whatever Interface they choose.

This will be aligned, FOr additional features in Frappe crm, not in erpnext crm, the user will simply use the frappe crm, and vice versa.

Erpnext CRM, uses the standard concepts of LPO(Leads, Prospects, Opportunities)
the new Frappe CRM, uses, Deals Concepts. That should be a starting Point.

Both use and share, comapnies, as well as contats, thats a plus, however, some workflows, available in frappe crm, are not in erpnext crm, and vise versa, while the same recrods are used, you cant find them in eahc f the Suite,s merge these, its an easy fix, Maybe 1 Day worth of work.

The Status of Leads, in erpenxt crm, is very differently names, compared to status, in frappe crm, THis causes it to be that, Leads in frappe crm, cant be seen in erpnext crm, and similer leads in erpnext crm cant be seen in frappe crm. thats a good starting point, for merging these two in V16.

Among others, then in future as you say v17, work on remoing the one, and retaining only one.

@ankush is it possible to get an official, App compatibility for V16 Page, Where each App provider, can list if their Apps i compatible with v16 or not

Hey @compgeniuses ,

There is this page which shows app compatibility within the Frappe eco system.

Hello, I am facing an issue in version 16. While creating a workspace, the frontend is submitting the ‘app’ field with too many values, causing the backend validation to fail. Is it because of my settings?
params: {“content”:“[{\“type\”:\“header\”,\“data\”:{\“text\”:\“工单变更单\”}}]”,“name”:“工单变更单”,“label”:“工单变更单”,“title”:“工单变更单”,“public”:1,“for_user”:“”,“icon”:“funnel-plus”,“parent_page”:“Manufacturing”,“is_editable”:true,“selected”:true,“app”:{“app_name”:“erpnext”,“app_title”:“ERPNext”,“app_route”:“/app/home”,“app_logo_url”:“/assets/erpnext/images/erpnext-logo.svg”,“modules”:[“EDI”,“Subcontracting”,“Bulk Transaction”,“Telephony”,“Communication”,“Quality Management”,“ERPNext Integrations”,“Regional”,“Maintenance”,“Portal”,“Assets”,“Utilities”,“Support”,“Stock”,“Manufacturing”,“Setup”,“Selling”,“Projects”,“Buying”,“CRM”,“Accounts”],“workspaces”:[“Accounting”,“Assets”,“Buying”,“CRM”,“Financial Reports”,“Home”,“Manufacturing”,“Payables”,“Projects”,“Quality”,“Receivables”,“Selling”,“Settings”,“Stock”,“Subcontracting”,“Support”]},“type”:“Link”,“link_type”:“DocType”,“link_to”:“BOM Operation”}