Category:RoadMap: Difference between revisions

m
mNo edit summary
Tags: Visual edit Mobile edit Mobile web edit
Tags: Mobile edit Mobile web edit
Line 60: Line 60:


In short, if you have ideas for increasing the number of “FDKs”, or encouraging actors to convert from business developers to FDKs, it is welcome, because this is the bottleneck and where the project is at risk (the problem is that business developer sells their production to customers so we have a large amount of such contributions, but not the FDKs). If we find a “trick” to motivate actors to take on this role in support of the handful of existing FDKs, Dolibarr project will be taken on another dimension…
In short, if you have ideas for increasing the number of “FDKs”, or encouraging actors to convert from business developers to FDKs, it is welcome, because this is the bottleneck and where the project is at risk (the problem is that business developer sells their production to customers so we have a large amount of such contributions, but not the FDKs). If we find a “trick” to motivate actors to take on this role in support of the handful of existing FDKs, Dolibarr project will be taken on another dimension…
==What about Long Term Support (LTS)  version ?==
It is common to integrate bug fixes in version N, N-1 or N-2 (because it makes life easier for the developer to not go back too far), but any bug fix, submitted in even a very old version of Dolibarr (N-x), is integrated (if the PR respects the best practice of the "minimal change for bug fix" of course). All versions of Dolibarr are therefore open to a LTS process. However, in reality, few developers submit fixes for versions beyond N-2, so very old versions are maintained when maintenance contributions are submitted, but because few contributions are submitted for very old version, you must admit that there is only a limited maintenance support for very old versions.


=Branch and Source control management=
=Branch and Source control management=