I was under the impression feature would only go into the develop branch and likewise future releases of ERPNext. Stable branches only received fixes.
Because I believe it may be beneficial to the entirety of the Community to understand the release process/policies I’d like to understand what the criteria is for features to be added to a stable release (like v12 in this example).
Can someone with insight in the process kindly clarify on this?
@vrms Except for Appointment Scheduling, others are small features that are needed for some business. We are sending the PR related to new features on to the develop branch only but there are some edge cases for which we need to send the PR on the stable version.
Regarding Appointment Scheduling, it’s a completely new feature and there will be no impact on existing stable features.
It gets more chaotic with every release isn’t it?
No idea where the product is heading thus have no idea where to contribute.
Lots of things happening without any proper knowledge about the problem domain and a proper state of design approach.