We are planning to release Version 16-beta on 1st June '25 and final release on 1st August '25
Many of the features in V16 are already backported to V15. There will be many more performance fixes and UI updates. There is no specific reason other than ensuring a regular release cycle.
@nabinhait will update the planned feature list.
with this being said
and this fact at hand,
wouldnt just focusing on imporving the UI, to be more more close with frappe crm, accross products be great for a v16.
otherwise i think everyone will still be ok with v15 as is, if still has great features, functionality improvements, and bug fixes.
In version 16 most of the UI are in vuejs like it’s in crm app?
Ah interesting, looking forward to this new release with the new UI components improvements.
And i hope most Apps resolve the Sidebar menu issue, where some frappe apps do not have the means to directly access other apps.
And on some new images i have seen, Frappe HRM, seems to be able to run independetly with its dedicated UI outside of erpnext, is this the case starting with erpnext 16?
Perfect and thanks for the update! Is there already a planned feature list available somewhere? Or not yet?
I don’t understand the race to V16 when bug reports are ignored in previous version. Why not work on a fully functional V15 first? ERP systems are core to business continuity. Stability is way more important than shiny new features. ERPNext should operate on a five-year release cycle like LTS versions of Linux.
I think this is a false dichotomy. Version 16 has explicitly focused on stability over new features, and a tremendous amount of the work that’s been done has been continuously backported to v15 and v14. I’m not aware of many new features I’d call shiny.
The UI/UX update is the biggest non-backported change I’ve noticed in the development branch, and it’s an important one. The foundations of the Desk interface go back many years now. Frontend technology has changed dramatically since it was first designed, and this tech debt has a real maintenance cost. There’s a lot more at stake here than just shine.
If you’re struggling with bugs, Frappe gives you a seat at the table to direct fixes for $38/month. That is an astonishingly good deal.
@volkswagner
I agree with @peterg . Also, 2088 is not just bugs; it’s a mix of bugs and feature requests. The bugs(not actual bugs, its bug label) are only 666, and out of these 666, many are old issues that may have already been fixed.
I feel ERPNext has become very stable, especially from v14. They’re mostly working on making it strong and adding a few new things, mostly for business use.
I also think we users should help more by reporting bugs properly or even try fixing them if we can. Many are already doing this, but we need more people to join. Compared to other frameworks, Frappe is just amazing, no doubt everyone here agrees!
Looking forward to the v16 
May from v16 we can name ther version just like ubuntu, android and others do…
@ejaaz You shouldn’t be too dismissive. Many issues are still valid, I haven’t seen any acknowledgement let alone a fix for issues I have reported. Plus this is just one repo, issues are moved to other repo of opened in incorrect repo.
Honestly not fixing issues had made me stop using erpnext. I was thinking to try afresh and set it up again but the dismissive behaviour doesn’t inspire confidence.
Hi @jhimtapaak:
Since thousands of people are using ERPNext and other Frappe apps, it’s absolutely normal to see a lot of issues. Many of them are being fixed, by maintainers and contributors, but still there are a huge amount of work to do.
Feel free the help. There are many ways:
Just complaining will not work 
Thanks.
Validating issues (reproduce it on your enviroment). Often we can see cases that are not really issues (just local behavior, missconfigurations, feature requests …)
I’m not stupid. I specifically mean bug reports, bugs which always reproduce.
Check if a problem is solved. Propose closing.
Genius.
Send PR and fix it.
No acknowledgement and your dismissiveness doesn’t inspire confidence. Far larger project maintainers are more responsive.
Honestly thinking the other guy is stupid just rubs off the wronr way.
This guy attempts to directly point out the problem in the code. You gonna say he doesn’t know his shit?
I’m not anyone to say this, so I will not do it.
I can point to specific code for an issue, but this would not the cause. I can say this too because have exactly experienced this before.
No one call you stupid, to you or anyone neither.
Anyway, this is a (truly) open source project.
If anyone can identify the wrong code … probably can send PR too.
If you need inmediate resolution, Frappe and partners offers paid support services.
Thanks.
I get both points. Bugs not getting fixed can be frustrating, but handling a large open source project isn’t easy either. Maybe if important issues are highlighted properly, they can get attention faster 
. At the same time, if more people pitch in, things can move quicker 
.
End of the day, open-source is all about teamwork 
. Let’s keep it positive and work together! 
