Actually I maintain 22 modules, some are simple, some are complex. To test all of them correctly (use all feature, modify doc, …) each time a new major version of Dolibarr is release is more than 2 full weeks long for Romain an me...
During the month a new version comes out, sales of modules on dolistore are halved cut (according to my information it is not related to my modules only).
I could do as some others … , just change the version number and wait for my clients put bugs me but I do not find it honest
Most integrators with whom I work no longer wish to upgrade versions as there are no major advances between two versions either-called major
The final version of each major costs money and energy to NOTHING: just to show that development teams are able to release two versions per year, two versions full of vacuum .
We have all been waiting for new accountancy module for 2 years. The time spent to release a new version will have better been employed to work on this strategic module…
Bien cordialement,
Charlie Benke
Hi
Thanks to Camille for pointing the main problem : Module and ratio time spend / bug / patch
As integrator of Dolibarr, it's not "sustainable" for me to test every six month Dolibarr and the modules I'm commonly using. Today I only install 3.9. Maybe next year, I will uprade to 5.0 or not... depending of what functions will be added or remaining experimental.
Modules are too often broken by new version. On the Dolistore you can see module labeled 3.x-4.0 who are in fact broken with the last version or doesn't exist for the current version of Dolibarr. I think it's not good for the reputation of Dolibarr.
I'll be pleased to discuss about this subject in Valence :-)
Regards
Philippe Scoffoni - Open-DSI
Hi
I agree, Dolibarr migration is pretty nice !
but only core part, modules looks more problematic to update.
Regarding communication, this is a work in progress.
Yes I saw this :) But looks again difficult. But it's better :)
From now on, we'll have systematic annoucement when a major version is released, minor version too, why not. A communication group has been started within the fundation with the goal to better communicate with the community. We already are present on social medias, but this dev mailing-list and the dolistore customers are 2 audiences we poorly communicate with (not to say not at all).
I don't understand logic, dolibarr users/community are on forum, mailinglist but piority is social network, strange
About your concerns around PRs and plugins, I'm sorry you feel that way. PRs are usually correctly integrated and not lost.
Maybe now, I'll try again. But I'm not sure. My fear is to lost again energy to nothing.
Plugins are the responsibility of their developers. Personnaly, our plugins are upgraded with the new releases
I'm not module developper then I don't know if is complicate or not to follow release and provide. As user, i prefer to have my own script and don't use module. In my use case ratio time spend / bug / patch is too heavy.
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev