Once again more explicit
Dolibarr 3.9 / RoadMap
Dolibarr next version 3.9.0 should not integrate new functionnalities but 2 major new features that many users have been waiting for:
n Accountancy
n Multi-currency
Evolution:
From 3.8.1 branch to launch 3.9 branch and keep the current development branch for future version 3.10
Annual versions:
2 annual versions to differenciate Dolibarr
A « PRO » version that would contain only functionnal evolutions, marked with an odd figure (ex : 3.9.x)
A « CORE » version that would contain only technical evolutions, marked with an even number (ex : 3.10.x)
Seasonnality
High season from september to march and à quiet season from April to August
Retroplanning
Within the high season : must be available a « PRO » version as stable as possible or event better a X.Y.2 version completed and available beginning of september.
It means that X.Y.1 version is released end of June and that X.Y.0 is released on April.
About « CORE » version, its development where developers could discuss about new features to add would be launched after the April DevCamp.
The .0 version release would be on end of september, a corrected version would be availbel in the end of the year et would be used as the base of the next « PRO » version.
About maintenance :
« PRO » version should be maintained 2 years long or 3. « CORE » versions only one year.
Versions | 1 | 2 | 3 | 4 - DevCamp | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
PRO | | | | X.Y.0 | | X.Y.1 | | | X.Y.2 | | | |
CORE | | | | X.Y-1.2 | | | | | X.Y+1.0 | | | X.Y+1.1 |
2016 Versions | 1 | 2 | 3 | 4 - DevCamp | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
PRO | | | | 3.9.0 | | 3.9.1 | | | 3.9.2 | | | |
CORE | | | | 3.8.2 | | | | | 3.10.0 | | | 3.10.1 |
2017 Versions | 1 | 2 | 3 | 4 - DevCamp | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
PRO | | | | 3.11.0 | | 3.11.1 | | | 3.11.2 | | | |
CORE | | | | 3.10.2 | | | | | 3.12.0 | | | 3.12.1 |
Targets
This organisation will give the ability
- To be ensured of a stable version for new users
- To have a version to work and make experiments for developers.
Bien cordialement,
Charlie Benke